Hi! There’s a new update for the Mapillary Desktop Uploader. You can download it from https://www.mapillary.com/desktop-uploader and your installed app should also automatically update to the new version from today.
What’s new in 5.0
Improvements to processing and upload speed.
New upload progress view which shows the uploaded size and estimates remaining time.
Video GPS tracks can now be edited on the map before upload.
We’re now using the latest version of ExifTool which brings support for more cameras.
Yes, congratulations, because you know how to make it difficult for someone to use the app.
So I go to Upload History, and instead of being able to quickly check which folders I’ve sent, as before, now I have to click on the three dots, select Show file, and scroll through several hundred lines of text… to see which folders I’ve sent.
Very intuitive for those who send two photos, maybe, but if you send 10 folders with 500 photos each, then scroll through and check.
Now, as for the app itself, I should have reported this a long time ago because it was the same in earlier versions. Just launching it when we have a very large number of sequences sent takes a minute to load for me (at least now).
The task manager shows that when it starts up, it continuously writes to the disk at about 15MB/s for a minute.
When I delete the entire Upload History, the application starts up much faster, and I noticed this a long time ago, but apparently others use faster disks and may not see it.
No faster disks, but unfortunately most people just suffer in silence.
Often people are simply unaware that many things are not a given but could be designed or made better. Sometimes, they are too tired or life has made them miserable from experiencing too many disappoints to voice any concerns or remarks. They lost belief in that things can improve.
We have already talked about this issue. @tao is going to improve upload history performance in the next release.
So I wanted to look at a few photos before sending the sequence, I don’t know, maybe I looked at 20 and closed the Image Viewer window - it popped up. After clicking OK, the desktop uploader shut down.
There is nothing about it in the logs -
[2025-10-05 07:17:37.920] [debug] [mapillary:tools] 07:17:37.925 - INFO - ==> Process summary
[2025-10-05 07:17:37.920] [debug] [mapillary:tools] 07:17:37.927 - INFO - 949 image read in total
[2025-10-05 07:17:37.920] [debug] [mapillary:tools] 07:17:37.928 - INFO - 949 (545.7 MB) ready
[2025-10-05 07:17:38.086] [debug] [mapillary:tools] process exit code 0 and signal null
[2025-10-05 07:17:38.288] [info] [services:mapillary:exif-worker] Reading mapillary_image_description.json
[2025-10-05 07:17:50.531] [info] [store:modules:config] API_URL: https://graph.mapillary.com/
[2025-10-05 07:17:50.585] [info] [mapillary:tools] Path to mapillary tools C:\Users\Rudd\AppData\Local\Programs\mapillary-desktop-uploader\resources\static\mapillary_tools\win32\mapillary_tools.exe
[2025-10-05 07:22:25.494] [info] Initializing app
[2025-10-05 07:22:25.501] [info] appName Mapillary Uploader
[2025-10-05 07:22:25.501] [info] appVersion 5.0.1
hello, been trying to upload 360 and none 360 imagery. however the result is the same and this error comes up. have tried a clean install, remove my C:\users\xxx\AppData mapillary folders, none of it sorted. can i download an older version of the uploader, searched but couldn’t find it.
5.0.2 update is out now. It includes a fix for the JS error reported by @czecko , brings back the folder names in the upload history and updates the app to the latest version of Electron for improved performance on the latest version of macOS.
First of all, thank you very much for the new version.
I’m not sure if I’ve found a problem in the Mapillary Desktop Uploader – or if something on my end isn’t working?
My initial situation:
I usually take my recordings with a GoPro Hero 8 while cycling.
Depending on the terrain conditions I use two different shooting modes:
Time-lapse: Creates still images (JPEG) with a resolution of 4000 x 3000 px. The best image quality shows the most detail, but this mode is not recommended if the terrain causes too much shaking. Also allows easy adjusting image positions during post processing if GPS data are incorrect.
Video: Creates MPEG4 videos with a resolution of 3840 x 2160 px. The image quality is not as good, but the HyperSmooth function ensures less camera shake. If GPS data is incorrect, corrections are next to impossible.
Therefore, I switch back and forth between the two modes during longer trips to get the best possible result depending on the ground.
Problem description:
Image sequences from GoPro MPEG4 videos (uploaded with Mapillary Desktop Uploader) are displayed on Mapillary with a time shift of +2 hours to the original creation time.
therefore video sequences are sorted to the wrong place in the listing of all the sequences of a shooting day.
Steps to reproduce:
Set the current date and time on the GoPro using the GoPro Quik app on a smartphone connected by Wi-Fi.
Create a GoPro MP4 video (H.264+HEVC) with GPS enabled.
Upload the MP4 video using Mapillary Desktop Uploader 5.0.x on macOS.
Check the image sequences timestamps of the uploaded videos.
Expected behavior:
Images extracted from videos should display the correct creation timestamps of my time zone.
My current time zone: CEST (Berlin/Germany), which corresponds to GMT+2.
Observed behavior:
Images from uploaded videos show a creation time with a time shift of +2 hours.
Additional information:
Images from uploaded still images created during the same recording show the correct creation time (mass upload with mapillary_tools to outsource the job to a headless Linux server).
Please feel free to ask for additional information if needed.
Thanks for reporting! It seems that we might not be extracting the timestamps correctly (looks like the timezone information might be lost) from the video during processing after upload. Can you send a sample video to support@mapillary.zendesk.com to help with debugging?
@GITNE - does deleting upload_history solve this problem for you? (e.g. how long does it take to start before/after?). @nikola - do you think this can be moved to an async load perhaps?
Desktop Uploader stores mapillary_tools at C:\Users\<user>\AppData\Local\Programs\mapillary-desktop-uploader\resources\static\mapillary_tools\win32 for me. Regardless, there is no upload_history file/folder there.
Desktop uploader and the included mapillary_tools keep an upload history (DU stores information about upload sessions and MT about the individual files). We’ll look into the app start up process and loading. History should be loaded only when needed (when viewing upload history and processing/uploading) but there might be other things that affect loading times.
Purging the upload history does improve mapillary_tools launch time for me when using the upload command. I do not use the Desktop Uploader, so I cannot tell for sure that this workaround is going to work for it too but since the DU builds on mapillary_tools the situation suggests itself that it should. For me, mapillary_tools takes increasingly more time to launch with every sequence uploaded when using the upload command.
