Your Polarsteps photos, back on the day and place of each step.
The data export Polarsteps sends you has every photo and video as a file named with random IDs, like 3f2a9c1e…_b7d4….jpg, with no date and no place inside. Both are in the trip’s trip.json. TripRedate matches each file to its step and gives it a real name, the step’s date and the step’s location, written into the file itself, right in your browser.
- Nothing uploaded, no Polarsteps login
- No Python, no ExifTool, no command line
- Works on a copy: your export is not changed
At a glance
What TripRedate does and doesn’t do
- Works withThe data export Polarsteps sends you: the ZIP as downloaded, or the extracted
user_datafolder. Each trip is a folder with atrip.jsonand one folder per step withphotos/andvideos/inside. Several trips at once. - RestoresThe date and the place of each step, on every photo and video of that step. It renames the file with the step date and name. It writes the date and the GPS coordinates inside the file: EXIF in JPEG photos (
DateTimeOriginal,OffsetTimeOriginal, GPS, place name), the creation date in MP4 and MOV. - Runs onThe browser on Windows, Mac, iPhone and Android. Nothing to install. No ExifTool, no Python.
- Free25 files per run, with the full manifest. Full: $9 one-time, every file.
- PrivacyNothing is uploaded. No Polarsteps login. Your photos and your trip stay on your device.
- Doesn’tRecover the exact time each photo was taken: the export has one date per step, so all photos of a step get that step’s date. It writes no date inside PNG or HEIC files (those are renamed and get a file date only) and no place into videos. It never invents a place for a step that has none. It does not rebuild the trip, its texts or its map. One run outputs up to 4 GB.
- Google Photos
- Apple Photos
- Windows Photos
- Lightroom
- Immich
- Synology Photos
each file is matched to its step by the ID in its folder name, not by a guess
How the match worksof your photos and your trip sent to any server
How it worksfiles redated free per run, with the full manifest of your export
Try itonce, every file, no subscription
PricingThe problem
A whole trip of photos, with random names and no dates.
“I downloaded my data from Polarsteps and the photos have random names and no dates. How do I get them back in order, with the days and places of the trip?”
Nothing on the file says when
The photos sit in each step’s photos/ folder with names like 3f2a9c1e-7b40….jpg and no date inside. Add them to Google Photos or Apple Photos and they all land on the day you downloaded them.
The date and place are in trip.json
Each step in trip.json has its time, its time zone, its name and its location with coordinates. No photo app reads that file.
Joining them is a script
The usual advice is ExifTool plus a script written for your export: walk the folders, look each step up in the JSON, convert the time zone, write the tags. Or fix every photo by hand.
How it works
Three steps. No Python, no ExifTool, no command line.
- Step 1
Get your data from Polarsteps
Ask Polarsteps for a copy of your data in your account settings. You get a ZIP with a
user_datafolder. Step-by-step guide - Step 2
Add the ZIP here
As downloaded, or the extracted folder. TripRedate reads every
trip.jsonand matches each file in a step’sphotos/andvideos/folder to its step by the ID in the folder name. - Step 3
Download the redated ZIP
One new ZIP: a folder per trip and step, files named with date, time and step name, the date and GPS written inside, plus a manifest.csv that maps every original name to its new name and step.
Redate
Open your Polarsteps export
Everything runs on this page. Your photos and your trip never leave your device.
Drop your Polarsteps data export .zip or the extracted user_data folder here
It must include each trip’s trip.json and the step folders with their photos and videos. Nothing is uploaded.
The date is the step’s date, in the step’s own time zone: the export has no time for each photo. GPS and the place name are written into JPEGs when the step has a location; no place is invented when it has none.
Free: 25 files per run and the full manifest. Unlock every file for $9.
Standard metadata
Written where photo apps already look.
No sidecar files, no special tags. TripRedate writes the same fields a camera or phone writes, so galleries, backup tools and file managers can read them.
- JPEG: EXIF DateTimeOriginal, CreateDate, ModifyDateThe field apps show as Date Taken, in the local time of the step, with
OffsetTimeOriginal(for example+02:00). The pixels are not touched. - JPEG: EXIF GPS latitude and longitude, ImageDescriptionThe coordinates and the name of the step’s location in
trip.json. Only when the step has them. - MP4, MOV: creation dateWritten in the
mvhd,tkhdandmdhdatoms, in UTC as the format requires. Nothing is re-encoded.
$ exiftool -DateTimeOriginal -OffsetTimeOriginal -GPSPosition -ImageDescription "2025-06-14_1630_Lake Como_1.jpg"
Date/Time Original : 2025:06:14 16:30:00
Offset Time Original : +02:00
GPS Position : 45 deg 59' 11.04" N, 9 deg 15' 25.92" E
Image Description : Lake Como (Bellagio, Italy)Original file, New file, Step, Date used (local), Place, Status
lake-como_98765432/photos/3f2a9c1e…jpg, Italy 2025/2025-06-14 Lake Como/2025-06-14_1630_Lake Como_1.jpg, Lake Como, 2025-06-14 16:30:00, Bellagio, written
lake-como_98765432/videos/51d9f0c7…mp4, Italy 2025/2025-06-14 Lake Como/2025-06-14_1630_Lake Como_4.mp4, Lake Como, 2025-06-14 16:30:00, Bellagio, renamed only
old-step_11111111/photos/a07c2b55…jpg, not-in-trip/old-step_11111111/a07c2b55…jpg, , , , not matched to a stepWhat you get back
Every photo and video on its day, named after its step.
The export keeps each step’s files in a folder named with the step’s ID, and trip.json has each step’s date, time zone and location. TripRedate joins them file by file.
Matched by step ID
Each file in a step’s photos/ and videos/ folder is matched to its step by the number at the end of the folder name, which is the step’s id in trip.json. Several trips in one export are handled.
Date inside the file
Writes DateTimeOriginal into each JPEG, in the step’s local time with its UTC offset, and the creation date into MP4 and MOV. Not just a file date that changes when the file is copied.
Place in the name and in the GPS
Files like 2025-06-14_1630_Lake Como_1.jpg instead of 3f2a9c1e-7b40….jpg, and the step’s coordinates as EXIF GPS in JPEGs. No place is invented when the step has none.
Dates already inside respected
A photo or video that still carries its own date keeps it unless you tick the overwrite box. The original extension is always kept.
Private, and on a copy
There is no upload step and no Polarsteps login. Your export is only read; you get a new ZIP with the copies.
A CSV that maps every file
manifest.csv lists every file: original name, new name, trip, step, step time, time zone, place, country, coordinates, the first words of the step text, what was written and its status.
Compared
Three ways to deal with the photos of a Polarsteps export.
The free routes work and keep your files on your computer too. TripRedate is for getting dates, places and real names onto the files without writing a script.
| Feature | TripRedate | ExifTool + your own script | By hand in a photo app |
|---|---|---|---|
| What it is for | Dating, placing and renaming the export’s photos and videos | Writing any metadata into any file; the usual advice for this job | Fixing a handful of photos |
| Cost | Free for 25 files, $9 once for all | Free | Free |
| Reads trip.json and matches files to steps | Yes, automatically, by step ID | You write and debug that part yourself | You look each step up yourself |
| Renames each file with its step date and name | Yes | If you script it | One by one |
| Writes the date inside photos and videos | Yes: EXIF in JPEG, creation date in MP4, MOV | Yes, any field you script | Depends on the app: some change only their own library |
| GPS from the step’s location | Yes, in JPEGs | Yes, if you script it (videos too) | You type or pick each place |
| Exact capture time of each photo | No: the export only has the step’s date | No: the export only has the step’s date | Only if you remember it |
| PNG, HEIC dates inside the file | No: renamed and file date only | Yes, ExifTool can write them | Depends on the app |
| What you install | Nothing | ExifTool and a script language such as Python | Nothing new |
| Your original files | Only read; you get a new ZIP | Depends on the options you pass | Depends on the app |
| Files leave your device | Never | Never | Depends on the app |
Pricing
Free for 25 files. $9 once for all of them.
Start free
Free
Redate 25 files per run and see the full manifest of everything in your export.
Redate my trip photos- Full manifest: every file and its step
- 25 files renamed, dated and placed
- Trip and step folders, manifest.csv
- No account
ONE-TIME
TripRedate Full
one-time · every file · any number of exports
Unlock every file, $9- Every photo and video in your export
- Several trips in one run
- Run it again on future exports
- No subscription
FAQ
Questions about Polarsteps export photo dates
Want the long version? Read the guide.
Read the guideWhy do my Polarsteps export photos have random names and no dates?
In the data export Polarsteps sends you, every photo and video is a file named with two random IDs, like 3f2a9c1e-7b40-4d1a-9e55-0c2d8a41b6f7_b7d4e0a2-1c35-4f6e-8a90-5d3e7f219c44.jpg, inside the folder of its step. The name says nothing about the day. In the real export we tested, none of the 18 JPEGs had a capture date or GPS inside either, so a photo app has only the file date to go by, which is the day you downloaded or unzipped the export. The dates and places are in the same export, in each trip’s trip.json file. TripRedate reads it and puts them on the files.
How does it know which step a photo belongs to?
By the folder, not by guessing. Each trip is a folder with a trip.json and one folder per step, named with the step’s slug and its ID, for example lake-como_98765432, with photos and videos folders inside. The number at the end of the folder name is the id of a step in trip.json. TripRedate looks that step up and gets its date, time zone, name and location. trip.json itself does not list the photos.
Which date does it write, and in which time zone?
The date and time of the step: its start_time in trip.json, which Polarsteps stores as a UTC timestamp next to the step’s time zone (for example Asia/Tokyo). TripRedate converts it to the local time of that zone, daylight saving included, and writes that as the date, plus the offset from UTC as OffsetTimeOriginal. A step at 4:30 PM in Italy is written as 4:30 PM wherever you run the tool.
Is that the exact moment each photo was taken?
No. The export does not say when each photo was taken: trip.json has one date per step and no date per photo. Every photo and video of a step gets the date and time of that step, so they land on the right day and in the right place in your trip, in step order, but several photos of one step share the same time. If a file still carries its own camera date inside, that date is kept.
Does it write the place and GPS?
Yes, the step’s. Each step in trip.json has a location with a name, a country, a latitude and a longitude. TripRedate writes those coordinates into each JPEG as EXIF GPS, writes the step and place name as the EXIF ImageDescription (for example “Lake Como (Bellagio, Italy)”), and puts the step name in the file and folder name. These are the coordinates of the step, not of the spot where each photo was taken. When a step has no coordinates, no GPS is written: nothing is invented. GPS is written into JPEG photos only, not into videos. A JPEG that already has GPS inside keeps it.
What if a photo or video already has a date inside?
It keeps it. By default TripRedate does not replace a DateTimeOriginal that is already in a JPEG, or a creation date that is already in a video: that date came from the camera or the phone. Those files are still renamed with the step date, and GPS is added to a JPEG if it had none. If you want the step date stamped into every file anyway, tick “Overwrite dates already inside files”. manifest.csv says, file by file, what was kept and what was replaced.
What does it do with videos?
For MP4 and MOV files it writes the creation and modification date in the file’s own headers (the mvhd, tkhd and mdhd atoms), which is where video apps read it. Nothing is re-encoded. In the real export we tested, the one video already had a creation date inside, about 45 minutes before the time of its step, so by default it was renamed and kept that date; with the overwrite box ticked it got the step date. That test covered one MP4; MOV uses the same code but we had no real MOV to test. No place is written into videos.
What about PNG, HEIC and other file types?
They are renamed with the step date and name, sorted into the same folders, and get the date as their file date in the ZIP. No date is written inside them: their bytes are copied untouched. The real export we tested held only JPEG photos and an MP4 video.
What do the new names and folders look like?
A folder per trip and per step, and the date, time and step name in each file: Italy 2025/2025-06-14 Lake Como/2025-06-14_1630_Lake Como_1.jpg. Several files of one step get _1, _2, _3, photos first, then videos; the export does not record the order they had in the app. The original extension is kept. You can also choose folders by year and month (2025/06/).
What happens to files that do not match a step?
They are not dropped. A photo in a folder whose number is not a step of the trip.json next to it is copied unchanged into a folder named not-in-trip, and a file of a step that has no readable date goes into no-date. Both are listed in manifest.csv with that status.
How do I get my data export from Polarsteps?
Ask Polarsteps for a copy of your data: in your account settings, under privacy, there is an option to download your data. Polarsteps prepares a ZIP and sends you a link. Inside is a user_data folder with a trip folder that holds one folder per trip. Add that ZIP here as it is, or the extracted user_data folder. Polarsteps can move this option; if you cannot find it, search their help center for “download my data”.
Are my photos or my trip uploaded anywhere?
No. The files are read and the new ZIP is built by JavaScript on this page, on your device. There is no upload step and no Polarsteps login. The only network requests are for the page itself, cookieless page analytics, and the payment check if you buy the full version, which sends a payment ID and never a file.
Do I need Python, ExifTool or the command line?
No. Nothing is installed. It runs in the browser on Windows, Mac, iPhone and Android, and does the whole export in one batch. On a phone it is fine for a small export; for a long trip with many videos use a computer.
How big an export can it handle?
The export ZIP is read file by file, without unzipping it first. The limits are on the way out: the new ZIP of one run holds up to 4 GB and 65,535 files, and a single photo or video can be up to about 2 GB. If your trips add up to more than 4 GB, extract the export and add one trip folder at a time; files that do not fit are listed in manifest.csv, never dropped silently. We tested with a real export sample of 19 files and with a 3,000-file run of small test images; we have not tested a real multi-gigabyte export, which needs a computer with free memory.
Does it rebuild my trip, my texts or my map?
No. TripRedate only deals with the photo and video files. It does not show the trip, convert the step texts or draw the route. manifest.csv does carry, next to each file, its trip, its step, the place, the coordinates and the first words of the step text, so you can tell what each photo belonged to.
Does it change my original export?
No. The export is only read. You get a new ZIP with copies and decide what to do with it. In a JPEG only the EXIF block changes: the image data is copied as it is, nothing is re-compressed.
How does the $9 full version work?
Free processes 25 files per run and lists everything else it found in manifest.csv. The full version is a single $9 payment, with no subscription and no account, and processes every file, in any number of exports. It unlocks in the browser you pay from.
Put your trip photos back on their days.
Add the ZIP of your Polarsteps data export and get every photo and video back with its step’s date, its place and a name you can read. The first 25 files are free.