How to share your travel route with friends (without losing your photos)
You go on a trip. You take 200 photos. A friend asks "where did you go?" and you… what? Forward 47 messages from a WhatsApp group? Send an Instagram tag? Try to remember the order things happened in?
Most people who travel a lot have hit this wall. It's not that the technology doesn't exist — it's that every popular sharing method gives you about 60% of what you need, and a different 60% each time.
This is a practical guide to sharing your travel route as a single, complete artifact: photos, stops, the path between them, and your honest take on each place. With a friend who hasn't installed your app of choice. From your phone, in under five minutes.
The three default ways people share trips, and why each falls short
The group chat photo dump
You messaged 87 photos to the WhatsApp group while travelling. Six months later: you can't find the photo of the lunch place because it's mixed in with everyone else's contributions; the chronology is roughly intact but if anyone replied with a sticker, photos are scattered across screen-fulls of unrelated chat; and there's no map.
Worse: WhatsApp eventually cleans up media on free-tier devices. The photos may not be there at all in two years.
The Instagram tagged-location grid
We covered this one in detail in Why Instagram is a terrible place to log your travels — the short version: location tags don't store coordinates, the grid isn't ordered by trip, and the captions never get written.
If you want to send a friend "the trip", you'd be sending six separate posts and they'd have to mentally reconstruct the order.
The Google Maps starred list
This is the closest to working, weirdly. Star a place, drop it into a list, share the list as a link. Your friend can see the pins on a map.
What it's missing: any photos you took, captions or notes per place, an order between the stops, and any sense of when you went. Google Maps lists are an "I want to come back here" tool, not a "here's where we went" tool.
What "good" looks like
A travel route share, done right, has six things:
- A title and a date. "Lisbon, October 2025" or "Sunday in Whitstable".
- A list of stops in order. Café first, then the gallery, then the harbour, then dinner.
- A photo or two per stop. The ones you'd actually want to send a friend.
- One or two lines per stop. What it was, whether it was good, anything they should know.
- A map drawing the route. Even a rough line connecting the stops.
- A single URL. Something you can paste into a message, an email, a tweet, anywhere.
If a sharing method gives you fewer than five of those, it's not really doing the job.
The pattern that works: log as you go, share as a page
The thing that unlocks fast sharing is doing the boring work during the trip rather than after it. Most people try to assemble the trip in retrospect — and then it never happens, because retrospect-trip-assembly is a 2-hour project nobody wants to do on a Tuesday evening.
If you log each stop as you arrive — photo, one-line note, optional rating — the trip becomes a single shareable page automatically by the time you head home.
Here's how that looks in practice on venture out (the app this blog belongs to). The same pattern works on Polarsteps, Wanderlog, FindPenguins, and Journi — you'll be doing the same six things, with different button labels.
Step 1 — start the venture before you arrive
Open the app, tap "New venture", give it a working title ("Lisbon weekend"), pick a date. You don't need to plan the stops in advance. The venture exists as an empty container waiting for entries.
Step 2 — log each stop as you arrive
Open it. Tap "Add stop". Search the place name (it autocompletes from Google Places) or pick the pin off the map. Add a photo. Type a sentence — it can be one word ("amazing") or three ("burnt; left half"). Tap save. Total time: 30 seconds.
This is the only habit that matters. Do it every time you sit down at a place. The whole architecture rests on this one habit.
Step 3 — let the route fill itself in
Most travel journal apps draw the path between stops automatically — straight lines, walking routes, or driving routes depending on the app. You don't have to think about it. By the end of the trip the map looks like a real journey.
Step 4 — publish
When you're home (or right at the end of the last stop), hit Publish. The venture goes from a private draft to a public page with its own URL.
On venture out the URL pattern is https://www.ventureout.life/trip/{id} — a single-page render of your route, photos, stops, and ratings. No login required to view it.
Step 5 — share the link
This is the moment. Copy the URL. Paste it into:
- A WhatsApp message ("here's the Lisbon route")
- A reply to the friend who asked
- Your Instagram bio, if you want to redirect grid-watchers to the full thing
- An email
- A Notion page
- Anywhere
Anyone who taps it opens a real web page with a real map. They can scroll through every stop, see the photos, read the notes, and — on most travel-journal apps — copy the route and use it as the basis of their own trip.
Edge cases
"What if my friend doesn't want to sign up to view it?"
A good shareable trip doesn't require an account from the viewer. On venture out, FindPenguins, and Wanderlog, the public trip page is just a web URL — no login wall. Polarsteps requires the viewer to have the app to see some features, but the basic trip view is open.
If an app gates the view behind sign-up, that's a serious mark against it. Frictionless sharing is the whole point.
"What about real-time sharing — friends following along while I'm away?"
Polarsteps and FindPenguins both have a live-tracking mode where your route updates in their app or on a public link as you go. It's a separate feature from the post-trip share and it's a genuinely good fit for parents tracking a backpacking kid or a partner away on tour. Most other apps don't do live; the published-at-the-end pattern is more common.
If real-time matters to you, Polarsteps is the strongest option. If you only care about the share-after-the-fact, the choice is wider.
"What if I want to share with one specific person, not the public?"
Most travel journal apps support per-trip visibility:
- Public — anyone with the URL can view, and the trip appears in public discovery feeds.
- Unlisted / private link — only people with the URL can view, but it doesn't appear in public discovery.
- Private — only you (and explicitly invited people) can view.
Use unlisted for the "send to my mum, no need to be on the public feed" case. Use private for journal entries you don't want anyone to see.
On venture out, every venture has a visibility toggle in the publish step. Same on Polarsteps. Wanderlog defaults to private; you have to explicitly flip a trip to public.
"Can my friend get the route off the app and into their own planning tool?"
This is where export matters. Most travel apps let the trip owner export their route as GPX (a GPS interchange format) or KML (Google's format). The viewer of a shared trip usually can't, unless the app exposes a "copy this route" feature.
Apps that do let viewers copy a route into their own account: venture out (built around this — every public venture has a "Copy route" button), Wanderlog (clone trip), FindPenguins (manual). Apps that don't: Polarsteps, Journi, Day One.
If you're sharing with a friend who actually wants to go on the trip, the copy-the-route case is what you want. If you're just sharing the memory, it doesn't matter.
"What about a route I've travelled with someone?"
Some apps support multi-author trips — both people log stops into the same venture, the published page shows both bylines. venture out and Wanderlog both do this. Useful for couples, friend groups, or families travelling together where everyone has the camera roll.
The shareable URL is the same for everyone; the trip just has more authors on it.
The minimum viable workflow
If you're starting from zero and want to land somewhere reasonable in a week:
- Pick one travel journal app — see our Polarsteps alternatives roundup for options.
- On your next trip, log one stop per meaningful place. 30 seconds each.
- At the end, publish the trip.
- Send the link to one person.
The thing to optimise for is the in-the-moment habit, not the eventual sharing technology. The sharing is the easy part once the data exists.
FAQ
Can I share a route across different apps — e.g. my friend uses Wanderlog and I use venture out?
Generally not directly, but you can always send the public URL — your friend just clicks through and views it in their browser. Cross-app trip imports are still rare; you'd be re-typing stops manually if you wanted to recreate the trip in their app.
What's the file format for exporting a route?
GPX (most outdoorsy apps), KML (Google Maps), or JSON (newer apps). GPX is the most universal — you can import it into Strava, Komoot, Gaia GPS, and most planning tools.
Will the link still work in five years?
Depends on the app's lifespan. Polarsteps and Wanderlog have been around 5+ years and are commercially stable. Journi has been around longer. Newer apps (us included) are exactly as durable as the company behind them. Worth exporting your route as GPX as a backup if you care about the long-term archive.
Can I share a route privately — like, just to my partner, with no public URL at all?
Yes — most apps with a visibility toggle support a "Private" mode where the trip is only visible to you (or to specific invitees). The trade-off is that there's no public link to share; your partner needs an account on the same app to view it.
Is there a way to share a route that includes the actual GPS track, not just the stops?
If you tracked the trip with a GPS app (Polarsteps, Strava, a Garmin watch), the export will include the full GPS line. If you logged stops manually in a journal app, the route between stops is interpolated — usually close to right, but not the exact path you took.