Mapillary Desktop Uploader 5.0 is out now!

[nikola]

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.

Thanks for your feedback and happy uploading!

[boris]

Wohoo! Looking forward to hearing how this new version works for everyone - we are excited about these updates.

[czecko]

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.

[czecko]

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

[nikola]

Thanks for letting us know! This will be fixed in an upcoming update.

[pruutus]

I rarely praise, but this update is great, especially the speed of primary processing.

[nunocaldeira]

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.

[nikola]

Thanks for reporting! Seems something is wrong with the Mapillary Tools config file. We’ll improve error handling for loading configs to prevent this issue in the future. To fix it, you can remove the contents of the Mapillary Tools config folder which should be “C:\Users\username\.config\mapillary\configs”: mapillary_tools/mapillary_tools/config.py at 9040c78a82636d88959728ec66a423fbdfa77260 · mapillary/mapillary_tools · GitHub

[nikola]

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.

[Macsico]

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 in advance.

[nikola]

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?

[Macsico]

Thanks for your offer to check.

Email has been sent with a link to my web server as the 845 MByte sample file is way too big for an attachment.

Zendesk automatical answer: “Mapillary Request #37900 Received”

[HellPhoto]

It seems like every time I open DU, it takes longer and longer to load and it sits on this screen:

[2025-11-20 20:12:06.539] [info] Initializing app
[2025-11-20 20:12:06.546] [info] appName Mapillary Uploader
[2025-11-20 20:12:06.546] [info] appVersion 5.0.3
[2025-11-20 20:12:06.548] [info] appUserData C:\Users\...\AppData\Roaming\Mapillary Uploader
[2025-11-20 20:12:06.548] [info] process.platform win32
[2025-11-20 20:12:06.549] [info] process.arch x64
[2025-11-20 20:12:06.549] [info] process.env.NODE_ENV production
[2025-11-20 20:12:06.549] [info] process.resourcesPath C:\Users\...\AppData\Local\Programs\mapillary-desktop-uploader\resources
[2025-11-20 20:12:06.549] [info] process.argv [
  'C:\\Users\\...\\AppData\\Local\\Programs\\mapillary-desktop-uploader\\Mapillary Uploader.exe'
]
[2025-11-20 20:12:06.677] [info] Checking for update
[2025-11-20 20:12:07.031] [info] [store:modules:config] API_URL: https://graph.mapillary.com/
[2025-11-20 20:12:07.048] [info] [mapillary:tools] Path to mapillary tools C:\Users\...\AppData\Local\Programs\mapillary-desktop-uploader\resources\static\mapillary_tools\win32\mapillary_tools.exe
[2025-11-20 20:12:07.085] [info] Initializing renderer
[2025-11-20 20:12:07.366] [info] Update for version 5.0.3 is not available (latest version: 5.0.3, downgrade is disallowed).
[2025-11-20 20:12:07.366] [debug] checkForUpdatesAndNotify called, downloadPromise is null
[2025-11-20 20:12:26.350] [debug] unresponsive undefined
[2025-11-20 20:12:49.129] [debug] unresponsive undefined
[2025-11-20 20:13:21.587] [debug] [mapillary:tools] storing credentials
[2025-11-20 20:13:21.889] [debug] [store:modules:user] locale en-US
[2025-11-20 20:13:22.669] [debug] [mapillary:tools] Existing Mapillary profiles:
       Profile name                              User ID                         Username
    1. hellphoto                         ...                        hellphoto

[2025-11-20 20:13:22.669] [debug] [mapillary:tools] 20:13:22.669 - WARNING - The profile "hellphoto" already exists and will be overridden

[2025-11-20 20:13:23.189] [debug] [mapillary:tools] 20:13:23.189 - INFO    - Profile "hellphoto" updated: {'user_upload_token': '[REDACTED]', 'MAPSettingsUsername': 'hellphoto', 'MAPSettingsUserKey': '...'}

[2025-11-20 20:13:23.220] [debug] [mapillary:tools] process exit code 0 and signal null

[czecko]

Don’t worry, it only takes about 8 minutes to start up on my computer…

[boris]

@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?

[HellPhoto]

@GITNE

By default, on Windows Vista and later it should be in

C:\Users\<username>\AppData\Local\mapillary_tools\upload_history

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.

[nikola]

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.

[czecko]

As a quick workaround, try to delete the upload history.

C:\Users\<username>\AppData\Local\Mapillary\mapillary_tools\upload_history

and then you need to go to …AppData\Roaming\Mapillary Uploader

and delete config-(some numbers).json, and now Desktop Uploader launches in a few seconds.

[czecko]

No need to sign-in again.

[czecko]

Now, literally every day, when I want to send two sequences (two folders), everything is fine after the first sequence, but the second one gets “Upload failed, Error: We encountered an error. Please try again.”

[2025-12-12 11:26:47.703] [debug] [mapillary:tools] 11:26:47.713 - INFO - ==> Upload summary
11:26:47.713 - INFO - Nothing uploaded. Bye.

[2025-12-12 11:26:47.719] [debug] [mapillary:tools] Traceback (most recent call last):

[2025-12-12 11:26:47.719] [debug] [mapillary:tools] File “main.py”, line 8, in
File “mapillary_tools\commands_main_.py”, line 156, in main
File “mapillary_tools\commands\upload.py”, line 82, in run
File “mapillary_tools\upload.py”, line 121, in upload
File “mapillary_tools\upload.py”, line 112, in upload
File “mapillary_tools\upload.py”, line 631, in _continue_or_fail

[2025-12-12 11:26:47.719] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 573, in upload_images
File “mapillary_tools\uploader.py”, line 599, in _upload_sequence_and_finish
File “mapillary_tools\uploader.py”, line 594, in _upload_sequence_and_finish
File “mapillary_tools\uploader.py”, line 670, in _upload_images_parallel
File “concurrent\futures_base.py”, line 449, in result
File “concurrent\futures_base.py”, line 401, in __get_result
File “concurrent\futures\thread.py”, line 59, in run
File “mapillary_tools\uploader.py”, line 722, in _upload_images_from_queue
File “mapillary_tools\uploader.py”, line 767, in upload

[2025-12-12 11:26:47.719] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 809, in _get_cached_file_handle
File “mapillary_tools\history.py”, line 122, in get
File “mapillary_tools\history.py”, line 118, in get
File “”, line 811, in get
File “mapillary_tools\store.py”, line 99, in getitem
File “mapillary_tools\store.py”, line 87, in _execute
sqlite3.OperationalError: disk I/O error

[2025-12-12 11:26:47.719] [debug] [mapillary:tools] [PYI-7672:ERROR] Failed to execute script ‘main’ due to unhandled exception!

[2025-12-12 11:26:47.875] [debug] [mapillary:tools] process exit code 1 and signal null
[2025-12-12 11:26:47.891] [error] [store:modules:uploadSession] exit with code 1 and signal null
[2025-12-12 11:26:47.953] [info] [power-saver-blocker] stop: 1
[2025-12-12 11:26:47.969] [info] [services:observer-manager] Stopping 1f1b26f0-d73f-11f0-96ab-873bfbb3ede6
[2025-12-12 11:26:47.969] [error] [vue] { code: 1, message: ‘exit with code 1 and signal null’ }

So, I click Retry, the MB counter increases, and at the end we get the same message: “Upload failed, Error: We encountered an error. Please try again.”

[2025-12-12 11:47:48.596] [debug] [mapillary:tools] 11:47:48.595 - INFO - ==> Upload summary

[2025-12-12 11:47:48.597] [debug] [mapillary:tools] 11:47:48.597 - INFO - Nothing uploaded. Bye.

[2025-12-12 11:47:48.607] [debug] [mapillary:tools] Traceback (most recent call last):

[2025-12-12 11:47:48.608] [debug] [mapillary:tools] File “main.py”, line 8, in
File “mapillary_tools\commands_main_.py”, line 156, in main
File “mapillary_tools\commands\upload.py”, line 82, in run
File “mapillary_tools\upload.py”, line 121, in upload

[2025-12-12 11:47:48.613] [debug] [mapillary:tools] File “mapillary_tools\upload.py”, line 112, in upload

[2025-12-12 11:47:48.616] [debug] [mapillary:tools] File “mapillary_tools\upload.py”, line 631, in _continue_or_fail

[2025-12-12 11:47:48.619] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 573, in upload_images

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 599, in _upload_sequence_and_finish

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 594, in _upload_sequence_and_finish

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 670, in _upload_images_parallel

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “concurrent\futures_base.py”, line 449, in result

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “concurrent\futures_base.py”, line 401, in __get_result

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “concurrent\futures\thread.py”, line 59, in run

[2025-12-12 11:47:48.629] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 722, in _upload_images_from_queue

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 767, in upload

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\uploader.py”, line 809, in _get_cached_file_handle

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\history.py”, line 122, in get

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\history.py”, line 118, in get

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “”, line 811, in get

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\store.py”, line 99, in getitem

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] File “mapillary_tools\store.py”, line 87, in _execute

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] sqlite3.OperationalError: disk I/O error

[2025-12-12 11:47:48.645] [debug] [mapillary:tools] [
[2025-12-12 11:47:48.645] [debug] [mapillary:tools] P
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] Y
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] I
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] -
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] 7
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] 7
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] 7
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] 2
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] :
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] E
[2025-12-12 11:47:48.660] [debug] [mapillary:tools] R
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] R
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] O
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] R
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] ]
[2025-12-12 11:47:48.676] [debug] [mapillary:tools]
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] F
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] a
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] i
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] l
[2025-12-12 11:47:48.676] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.692] [debug] [mapillary:tools] d
[2025-12-12 11:47:48.692] [debug] [mapillary:tools]
[2025-12-12 11:47:48.692] [debug] [mapillary:tools] t
[2025-12-12 11:47:48.692] [debug] [mapillary:tools] o
[2025-12-12 11:47:48.692] [debug] [mapillary:tools]
[2025-12-12 11:47:48.692] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.692] [debug] [mapillary:tools] x
[2025-12-12 11:47:48.707] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.707] [debug] [mapillary:tools] c
[2025-12-12 11:47:48.707] [debug] [mapillary:tools] u
[2025-12-12 11:47:48.707] [debug] [mapillary:tools] t
[2025-12-12 11:47:48.707] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.723] [debug] [mapillary:tools]
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] c
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] r
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] s
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] i
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] p
[2025-12-12 11:47:48.723] [debug] [mapillary:tools] t
[2025-12-12 11:47:48.738] [debug] [mapillary:tools]
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] ’
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] m
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] a
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] i
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] n
[2025-12-12 11:47:48.738] [debug] [mapillary:tools] ’
[2025-12-12 11:47:48.738] [debug] [mapillary:tools]
[2025-12-12 11:47:48.754] [debug] [mapillary:tools] d
[2025-12-12 11:47:48.754] [debug] [mapillary:tools] u
[2025-12-12 11:47:48.754] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.754] [debug] [mapillary:tools]
[2025-12-12 11:47:48.754] [debug] [mapillary:tools] t
[2025-12-12 11:47:48.754] [debug] [mapillary:tools] o
[2025-12-12 11:47:48.754] [debug] [mapillary:tools]
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] a
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] n
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] d
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] l
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] d
[2025-12-12 11:47:48.785] [debug] [mapillary:tools]
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] x
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] c
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] e
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] p
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] t
[2025-12-12 11:47:48.785] [debug] [mapillary:tools] i
[2025-12-12 11:47:48.801] [debug] [mapillary:tools] o
[2025-12-12 11:47:48.801] [debug] [mapillary:tools] n
[2025-12-12 11:47:48.801] [debug] [mapillary:tools] !
[2025-12-12 11:47:48.801] [debug] [mapillary:tools]

[2025-12-12 11:47:48.754] [debug] [mapillary:tools] u
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] n
[2025-12-12 11:47:48.770] [debug] [mapillary:tools] h
[2025-12-12 11:47:48.926] [debug] [mapillary:tools] process exit code 1 and signal null
[2025-12-12 11:47:48.926] [error] [store:modules:uploadSession] exit with code 1 and signal null
[2025-12-12 11:47:48.973] [info] [power-saver-blocker] stop: 6
[2025-12-12 11:47:48.988] [info] [services:observer-manager] Stopping ef5f5ea0-d747-11f0-96ab-873bfbb3ede6
[2025-12-12 11:47:48.988] [error] [vue] { code: 1, message: ‘exit with code 1 and signal null’ }