# Mapillary Uploader 5.1.1 is out!

**URL:** https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365
**Category:** Contributing and equipment
**Created:** [May 6, 2026, 12:22pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365 "2026-05-06T12:22:41Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![nikola](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@nikola](https://forum.mapillary.com/u/nikola)
#### Post date: [May 6, 2026, 12:22pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/1 "2026-05-06T12:22:41Z")

</div>

Hi! We recently released a new update for the Mapillary Uploader, you can download it at [https://mapillary.com/desktop-uploader](https://mapillary.com/desktop-uploader) and your installed apps will auto-update the next time you start.

**Here’s what’s in this update:**

- Improved startup speed: we updated how we load upload history to reduce waiting time. We have also simplified the data we store in the upload history to prevent this issue from occuring in the future.
- We have also added a “Reset” button to the upload history.
- This update includes the latest Mapillary Tools: [Release v0.14.7 · mapillary/mapillary\_tools · GitHub](https://github.com/mapillary/mapillary_tools/releases/tag/v0.14.7)
- Also includes the latest ExifTool for improved camera compatibility.
- Some UI improvements like: the app will now ask you if you want to apply the update when it has been downloaded and the app will ask you to confirm if you want to close it while an upload is in progress.
- Fixed drag-and-drop on Ubuntu.
- Fixed issues with OSM map tiles.

Thanks for your feedback and happy uploading!

---

<div class="post-metadata">

### Author: ![czecko](https://avatars.discourse-cdn.com/v4/letter/c/e9c0ed/32.png) [@czecko](https://forum.mapillary.com/u/czecko)
#### Post date: [May 6, 2026, 4:19pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/2 "2026-05-06T16:19:41Z")

</div>

So what has been fixed or added in version 5.1.1?

---

<div class="post-metadata">

### Author: ![nikola](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@nikola](https://forum.mapillary.com/u/nikola)
#### Post date: [May 6, 2026, 4:46pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/3 "2026-05-06T16:46:30Z")

</div>

Ah, this one was is the OSM map tile fix. 🙂 We were in the process of releasing 5.1.0 just as this was reported so we wanted to include it (and also a couple ofther minor dependency updates) so 5.1.1 is the one we announce here in the forum. We’ll add more info on [https://www.mapillary.com/release-notes](https://www.mapillary.com/release-notes)

---

<div class="post-metadata">

### Author: ![osmplus\_org](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/osmplus_org/32/72465_2.png) [@osmplus\_org](https://forum.mapillary.com/u/osmplus_org)
#### Post date: [May 7, 2026, 4:26pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/4 "2026-05-07T16:26:58Z")

</div>

I’m currently experiencing massive upload problems with the Desktop Uploader on my Ubuntu quad-core machine. This forces me to manually initiate each upload sequence individually. Typically, the upload speed starts promisingly at the beginning of each sequence, but then continuously drops and stagnates at just a few megabits per second. This pattern repeats itself the next time I try to upload. My network speed is fine, and I just reinstalled Ubuntu on the machine, but there’s no improvement.

Could it be that the Mapillary Tools require a powerful graphics card? The system load on my Linux machine shows normal values ​​for all parameters, such as CPU usage and memory consumption.

Desktop Uploader 5.0  
Desktop Uploader 5.1.1  
Ubuntu 24.04.4 LTS  
Intel Core i5 7600 x4  
16 GB RAM

In principle, I would like the idea of ​​providing Mapillary with a remotely controlled client on my computers – for data processing and upload preparation – if this would improve the upload process.

---

<div class="post-metadata">

### Author: ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)
#### Post date: [May 7, 2026, 6:36pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/5 "2026-05-07T18:36:14Z")

</div>

> [@osmplus\_org](#):
>
> I’m currently experiencing massive upload problems with the Desktop Uploader on my Ubuntu quad-core machine. This forces me to manually initiate each upload sequence individually.

This is not a Desktop Uploader issue but a network infrastructure issue. See [Increasing upload problems](https://forum.mapillary.com/t/increasing-upload-problems/10368).

> [@osmplus\_org](#):
>
> Could it be that the Mapillary Tools require a powerful graphics card?

No.

> [@osmplus\_org](#):
>
> In principle, I would like the idea of ​​providing Mapillary with a remotely controlled client on my computers – for data processing and upload preparation – if this would improve the upload process.

😆 No, Mapillary is already short on staff and they surely do not want to manage even more hardware or software on the edge. It would not improve upload speeds or network stability either.

---

<div class="post-metadata">

### Author: ![nikola](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@nikola](https://forum.mapillary.com/u/nikola)
#### Post date: [May 8, 2026, 10:35am UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/6 "2026-05-08T10:35:54Z")

</div>

Hi! Your system specs seem fine and should not be a problem for uploading to Mapillary.  
In this kinds of situations the internet connection is the most common culprit (ISP/router) but it could be also bottlenecks like HDD speed or server-side throttling.  
Do you notice a similar problem when uploading to a cloud storage service (like Dropbox etc.) from your system?  
If not, we could also take a look at your uploader logs (Help → Logs) for more details.

---

<div class="post-metadata">

### Author: ![osmplus\_org](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/osmplus_org/32/72465_2.png) [@osmplus\_org](https://forum.mapillary.com/u/osmplus_org)
#### Post date: [May 9, 2026, 9:38am UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/8 "2026-05-09T09:38:03Z")

</div>

~~Thank you for your efforts. I have now switched my uploads to one at a time; this is much more time-consuming for me, but doable.~~

---

<div class="post-metadata">

### Author: ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)
#### Post date: [May 9, 2026, 1:14pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/9 "2026-05-09T13:14:45Z")

</div>

Right! Do not run multiple Desktop Uploader or `mapillary_tools` upload sessions concurrently on a single internet connection. They or rather the upload protocol are not designed for this (yet). It does not improve your throughput either. If anything it rather hurts your throughput.

---

<div class="post-metadata">

### Author: ![osmplus\_org](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/osmplus_org/32/72465_2.png) [@osmplus\_org](https://forum.mapillary.com/u/osmplus_org)
#### Post date: [May 9, 2026, 5:38pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/10 "2026-05-09T17:38:20Z")

</div>

> [@GITNE](#):
>
> Right! Do not run multiple Desktop Uploader

~~You misunderstood me; I only use a single desktop uploader installation. I select a single recording, start the upload process, and wait for a green success message. Once the indicator is green, I manually select the next file and start the next upload. With some uploads, I usually get an “Upload failed” message exactly one minute before the estimated upload time is due to end. I then confirm “Try again.” The desktop uploader then works on the upload for significantly longer and finally displays “Finishing,” sometimes generating twice the uploaded data volume of the file itself. After waiting a while, a success message usually appears. The entire process is no longer automatic; each recording has to be started manually. Ultimately, this process works. I already have a backlog of recordings. I’m not complaining; at least it works somehow.~~

There are now significant fluctuations in the upload speed. It usually hovers around 18 MB/s, but now the speed frequently drops to 0, only to suddenly recover. During these periods, the actual upload process is running.

~~My current workflow is pragmatic: I first upload all the recordings to GSV. Once that’s done, I run the Mappillary Desktop Uploader. However, However, GSV, which isn’t experiencing any connection drops, is already 60 records ahead, and this discrepancy is causing me to run out of memory.~~

---

<div class="post-metadata">

### Author: ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)
#### Post date: [May 9, 2026, 7:06pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/11 "2026-05-09T19:06:21Z")

</div>

I see. This sounds indeed really inefficient and laborious. @nikola Doesn’t Desktop Uploader move on to upload the next sequence when uploading a sequence (on the list) fails? Maybe we should have like a “retry all failed sequences” button or what the “Retry” button should generally do?

---

<div class="post-metadata">

### Author: ![nikola](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@nikola](https://forum.mapillary.com/u/nikola)
#### Post date: [May 11, 2026, 10:05am UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/12 "2026-05-11T10:05:26Z")

</div>

It should be pretty resilient when it comes to common upload problems (internet connection issues, temporarily going offline etc.) but there are some scenarios where it can decide that it can not proceed (you can see the code for that decision here: [mapillary\_tools/mapillary\_tools/upload.py at main · mapillary/mapillary\_tools · GitHub](https://github.com/mapillary/mapillary_tools/blob/main/mapillary_tools/upload.py#L602)). @osmplus_org can you please send your log file to [support@mapillary.zendesk.com](mailto:support@mapillary.zendesk.com) so we can diagnose the problem? Thanks!

---

<div class="post-metadata">

### Author: ![osmplus\_org](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/osmplus_org/32/72465_2.png) [@osmplus\_org](https://forum.mapillary.com/u/osmplus_org)
#### Post date: [May 11, 2026, 8:33pm UTC](https://forum.mapillary.com/t/mapillary-uploader-5-1-1-is-out/10365/13 "2026-05-11T20:33:35Z")

</div>

> [@nikola](#):
>
> can you please send your log file to [support@mapillary.zendesk.com](mailto:support@mapillary.zendesk.com) so we can diagnose the problem? Thanks!

**Vielen Dank!**

Thanks to the now working uploads, I’ve been able to almost completely clear my backlog. I have already sent my log file to the support address you provided.

Thank you very much for your help!  
Johann
