You mean where the two circles are visible?
Ok, I will look into that tomorrow
The 033 image comes from an INSP file (52 MB). The saturation is already within file without any further edits. The RAW file (DNG; 129 MB) comes without any further pre-process in saturation etc. Hope, that helps!
15,520px × 7,760px ≅ 120 MP
@boris Please update How can I upload imagery to Mapillary? – Mapillary to reflect the true resolution limit. Insta360 X Series – Mapillary may need some updates too. ![]()
While at it, I wish MapillaryJS would also finally solve [🐛] Zoom‑in limited by maximum texture size and Why does the view get blurry on Mapillary at higher zoom levels?, although I do understand that it adds complexity to rendering code. But, this code path would only run in canvases where GL_MAX_TEXTURE_SIZE is smaller than any image dimension. Afaict the overall performance impact should remain negligible. Watch out for (silent) GL_OUT_OF_MEMORY though!
Done, I’ve updated to reference the 200MP resolution limit - let me know if there are other things you see that need updating - thanks @GITNE !
So, in this mode 120MP (15520 x 7760) images are taken? With minimum interval setting 3 seconds? I have checked review video and it looks like minimum interval is 10 seconds? That is actually a lot ![]()
In this mode max resolution is only 8000 x 4000/7680 x 3840?
Unfortunately, the interval mode is slower when „3 sec“ is set. It’s more like processing time AND 3 sec, which is effectively 8 seconds
Indeed, the actual interval when set to 3 seconds in my case is between 8 and 9 seconds. I’ve contacted Insta360 about it - the least they could do (in my opinion) is tweak the firmware to 0 seconds so the actual interval would be pure processing time, between 5 and 6 seconds. So far, I haven’t gotten a response even though there have been a couple of firmware updates since. - And yes, in Timelapse video mode the maximum resolution is 8000 x 4000.
This would be indeed helpful ![]()
Great!
Thank you! 200 MP should practically suffice forever because afaik Google Maps has played with different 360° resolutions and they concluded that ~100 MP is like a natural barrier above which one does not gain much additional information in the street mapping scenario. I think they finally settled on 134 MP ≈ 16,384 px × 8,192 px.
Please also update and document other important limits:
- 110 GB video file size (as per Desktop Upload release notes)
- 50 MB image file size limit (traditionally, although not officially documented)
- 100 GB total sequence size (traditionally, although not officially documented)
These are mostly important for organizational contributors. ![]()
The 16K optical resolution limit is interesting. I think it’s realistic, as larger sensors than MFT would cause depth of field issues. I don’t know about the other limits, but afaik I uploaded >50 MB images without problems.



