Amsterdam in late October smells like rain on cobblestones and something fried from a snack window at midnight. The canal light at dusk turns everything amber — the bikes, the houseboats, the tourists trying to read paper maps in the wind. I was there for eight days, then took a train south to Ghent and Bruges, and by the time I got home I had 600 photos, a voice memo that cut out halfway through, and a very clear sense that none of it had been captured properly.
That's the thing nobody tells you about travel photography. You come home with all this material and you still can't share what it actually felt like. I sent a Google Photos album to my family. They said "looks amazing." That was it. The album sat there — 600 images sorted by timestamp, completely stripped of any sense of movement or story or the specific feeling of standing on a bridge in Ghent at 7am when the mist was still sitting on the water.
I tried making an Instagram carousel. I picked twelve photos, wrote a caption, and immediately felt like I was lying about the trip. Twelve photos from eight days in two countries, posted in one afternoon. It didn't feel like documentation. It felt like a press release.
A trip isn't a collection of images. It's a sequence of places and the particular quality of light and noise and cold air that connected them. Most tools for sharing photos completely ignore that sequence.
Finding Something Different
A few weeks after I got back, a friend mentioned she'd used something called Cinemaly to share her Japan trip — not as a social post, but as a file she sent directly to people. She described it as a map that moved. I looked it up mostly out of curiosity.
What caught my attention wasn't the feature list. It was the fact that nothing gets uploaded anywhere. I'd gotten quietly tired of feeding my travel photos into platforms that store them indefinitely, optimize them into their own formats, and show them in whatever order their algorithm prefers. The idea of a tool that just processes everything locally and gives you back a file felt almost old-fashioned in the best way.
I went back through my Amsterdam and Belgium photos that same evening.
What the Process Was Like
Sorting the photos by city
I pulled photos into rough groups — Amsterdam, the train journey, Ghent, Bruges. Nothing precise, just enough to attach the right images to the right places. It took maybe twenty minutes and I found photos I'd completely forgotten taking.
Adding the route and writing notes
I typed in the four stops and wrote a sentence or two for each one. Not a full diary entry — just the thing I most wanted someone to know about that place. For Amsterdam it was the flea market on Waterlooplein. For Bruges it was the way the whole city smells faintly of waffles in the morning. Small things, but specific ones.
Downloading the file
The whole compilation took under a minute. A single .html file landed in my
downloads folder. I opened it in my browser and sat there for a moment just
watching it work.
What the Result Felt Like
The map opens on Amsterdam and then, as you scroll, it flies south. You can see the actual geography — the Netherlands flattening into Belgium, the distance between cities made visible. Each place has the photos I attached to it, and the note I wrote, and a marker that pulses on the map.
It sounds simple described like that. But the movement matters more than I expected. Travel is directional. You go somewhere, and then you go somewhere else, and the fact that those places are connected by actual distance is part of what made the trip feel the way it did. Watching the map sweep from Amsterdam to Ghent to Bruges gave me something back that the timestamp-sorted album couldn't: the sense that I actually went somewhere.
I sent the file to my family the next day with a short note explaining how to open it. My mother, who is not technically adventurous, opened it in her browser and scrolled through it on her own. She called me afterwards and described specific photos. She mentioned the canal light.
Would I Recommend It?
For the kind of trip where you moved between places — a multi-city journey, a road trip, anything with a route — yes, without hesitation. The format suits travel in a way that albums don't.
It's less useful if you stayed in one place. A week in a single city produces a gallery, not a route, and Cinemaly is really built around the movement between locations.
The part I keep thinking about is the file itself. It's not stored anywhere I don't control. I can put it on a hard drive, email it, keep it for ten years. There's something satisfying about a piece of documentation that doesn't depend on anyone else's server staying online. The trip happened. The file records it. That feels like enough.
If you've got an untreated batch of travel photos from a multi-city trip sitting in your camera roll — the kind you keep meaning to do something with — it's worth an hour of your time.
If this sounds like something you'd use: cinemaly.app — free, no account.