Trip planning lives in a dozen browser tabs that you will never reopen. A Travel Glubler turns that pile into one page you can actually use, and share with whoever is coming with you.
This is the use case Glubler is genuinely well suited to: lots of websites, a natural hierarchy, and a reason to share.
Trying to squeeze every trip into one big Travel list is what makes trip lists unusable. A fresh Glubler each time keeps each one small enough to read, and you can still share a single link when it is time to book.
This is the part that saves the most time. Instead of saving a tab and moving on, glue it as you go.
On a phone, the browser extension is desktop-only, so paste the address into Glubler the same way. It takes a few seconds per save, which is far less than the twenty minutes you will otherwise spend hunting for something you saved in March.
If you already have a pile of links, Settings → Data → Import takes a CSV of them in one go rather than one at a time.
A flat list of forty links is hard to use on the ground. Nesting fixes that. On a Pro plan:
To add one, open the trip Glubler, click Create and choose Subglubler. It attaches to whichever level you are viewing, so open Kyoto first and it lands there.
No Pro plan? Make separate Glublers for Japan 2026 - Kyoto and Japan 2026 - Tokyo. Free, unlimited, and a link to each still works in a phone browser.
Things worth collecting for a trip, roughly in order of how often you will reach for them:
| Kind | Why it earns its place |
|---|---|
| Entry and visa rules | The one thing you will need offline, on a phone, before you land |
| Places to stay | Saved before you commit, so you can compare without losing tabs |
| Transport | Trains, ferries, airport transfers, and the local passes worth knowing about |
| Things to do | Attractions, neighbourhoods, day trips, walking routes |
| Food | Specific places worth the detour, not a general restaurant guide |
| Practical | Pharmacy, laundrette, SIM card, tipping norms, emergency numbers |
Glue the address of that hotel or that train line, not just booking.com. A Glubler of forty homepages is no use; a Glubler of forty specific pages is the whole trip in one place.
This is the step that makes Glubler better than a screenshot folder.
Two useful details:
Anyone you send it to can read it without an account, so there is nothing for them to sign up for.
Keep the Glubler. Trips you have taken are worth revisiting, and if you ever go back, everything you researched is still there.
Two tidy-up options:
Before a big change, such as clearing out old trips, export from Settings → Data → Export. A CSV is the only backup Glubler offers, and it is worth having.
No. Anyone can open a shared collection link and read it. Only creating an account lets them save and follow.
The Glubler itself needs a connection, but the links it holds still work when you have signal. Saving the handful of pages you need before you fly is worth doing.
Up to seven in total, counting the trip Glubler as the first. For most trips, two is plenty — the trip, then each city.
It is kept once across your account, and Glubler tells you rather than adding a second copy. If you genuinely need it filed in both, that is the one situation where exporting, deleting, and re-importing is worth it.
Yes. Leave a collection private and only you will see it, and a shared link to it will not display anything until you make it visible.