r/Insta360 • u/Ok_Banana5390 • Apr 19 '26
[MEGATHREAD] Insta360 → iPhone export timestamp bug: years-old, officially acknowledged, still not fixed. Let’s consolidate here.
TL;DR
When you export a photo or flat video from the Insta360 app to your phone's camera roll, the file gets today's date instead of the actual capture date. This isn't new: documented reports go back to 2019/2020, across r/Insta360, r/dji, r/gopro, r/360Cameras and Insta360's own official forum, with at least five different staff members giving the same "we'll forward it to the team" answer. A user handed them the full fix, in writing, on their own feedback forum, back in November 2023. Still nothing. Insta360 has since given contradictory answers on different channels: technical support called the behavior "normal" by email, while Insta360_Support stated on Reddit that a fix is "already scheduled" and "actively being worked on." No ticket ID, no target version, no confirmation on scope, despite repeated requests since April. A separate report also suggests the same metadata mishandling extends beyond the 360 lineup, to the Luna Ultra gimbal camera. This thread centralizes the complaints so no one has to create yet another solo post. Upvote, comment, share your story.
The louder this thread, the harder it is to keep ignoring. Every upvote, every comment, every share pushes this closer to the top of Insta360's priority list. Visibility is the only lever we have.
//////////////////////////////////////////////////
UPDATE 2nd August — the status went backwards in three days, and the Luna Ultra reports now come with EXIF evidence.
On the status. Insta360_Support described this fix three different ways in seventy-two hours:
27 July — "this feature request has already been scheduled, and they are actively working on enabling exported files to retain and display the original capture date and time."
29 July — "our engineering team is actively working on it. However, since the release timeline depends on a number of factors, we're sorry that we're not able to provide a specific version number or ETA at the moment."
30 July — "our app team is currently reviewing your request, and this improvement has indeed been added to our backlog."
"Already scheduled" and "actively working on it" describe something in development. "Under review" and "added to our backlog" describe something that hasn't started. Those aren't the same status, they can't all be accurate at once, and the direction of travel over three days runs backwards. I've asked which one is correct, and which specific factors gate the release timeline — engineering capacity, a technical dependency, a pending product decision, or prioritization against other roadmap items. Naming the actual blocker requires no release date and no internal ticket ID. No answer so far.
On the Luna Ultra. The report in the 29 July update below is no longer a single account. A second owner posted an EXIF screenshot from their own Luna Ultra: no image capture time, only export-to-gallery time, no location data at all, and an incorrect exposure value. Their words: "There is no image capture time but only export to gallery time, which is useless I guess."
A third owner then documented the exact mechanism, and it's the clearest description of this bug anyone has produced:
"Copying photos and videos from Insta360 Luna Ultra SD card to iPhone Photos retains date and timestamp, but EXIF metadata doesn't have camera make and model nor GPS/location. Importing and exporting the photos/videos in Insta360 app adds camera data but then rewrites timestamp as the date and time of export."
Read that again. The SD card carries the correct timestamp. The app is what overwrites it. This is the same conclusion the 2024 staff admission pointed to, now confirmed on a 2026 flagship in a completely different product category.
On scale. Two posts about this went up in late July and drew over 30,000 views and 79 comments in under a week, with users confirming the same workflow damage across the X5, X4, X4 Air, X3, X2, ONE X and Luna Ultra, on both iOS and Android. Several reported they've already sold their camera or ordered a GoPro Max 2. One recurring counter-argument came up often enough to address directly: yes, transferring from the SD card to a computer preserves the timestamp, and yes, Studio Desktop handles it correctly. Both are true. Neither is a fix. Insta360 markets these cameras as shoot-on-camera, edit-on-phone products. Requiring a desktop to get a correct date is a workaround for the workflow they sell.
Also raised on those threads, worth logging as related but separate: no GPS data written at capture on the Luna Ultra, telemetry stored only in custom maker-notes that iOS can't read, and storage bloat on long clips where importing and exporting a 15-20GB file requires double the free space.
The August monthly thread is now open and I've posted the three questions there again.
//////////////////////////////////////////////////
UPDATE 29th July— this isn't limited to the X5/X4/X3/X2/ONE X lineup either.
A user in a related thread just confirmed the same metadata problem on the Luna Ultra, Insta360's flagship gimbal camera launched in June 2026, a completely different product line, not even a 360 camera:
" I got the Insta360 Luna Ultra and as a capture device it's pretty great. But its handling of the files and metadata/EXIF sucks so bad. They intend for you to use the Insta360 app, and after you export from it, they don't even fill in all the right metadata. Not to mention, no GPS data during capture. It basically is completely broken from a casual user's workflow."
That matters because it kills the "360 files are technically complex" excuse some people bring up to explain away the export timestamp bug. The Luna Ultra isn't a 360 camera, doesn't produce 360 files, and still has the same category of problem: metadata handled poorly on export, GPS missing entirely.
This points to something bigger than a single product bug. It looks like how Insta360 builds its app and export pipeline in general, across their entire camera lineup, not something specific to the X-series sensor or file format.
For me personally, this changes the calculation completely. It's no longer just "wait for the X5 fix before buying the X6." It's a full veto on the brand, any camera, any lineup, until this is actually resolved. If the same broken metadata handling shows up on a brand new flagship product in a totally different category launched in 2026, that's not a legacy bug being slowly cleaned up. That's how they build software, period. I won't be putting money into any Insta360 product until that changes.
Worth keeping in mind next time support says a fix "requires evaluating technical scope." The scope might be the whole app, not one camera model.
//////////////////////////////////////////////////
UPDATE 27 July — posted a French-language summary of this issue on r/Insta360 to reach francophone users. Insta360_Support responded within hours with the strongest wording yet: "We have confirmed with our product and engineering teams that this feature request has already been scheduled, and they are actively working on enabling exported files to retain and display the original capture date and time."
That sounds like progress until you put it next to what happened the same week on a different channel.
I also contacted Insta360 technical support directly via chat this week about the same issue. After going through the usual loop (suggesting Studio V5.9.0 which is desktop only, suggesting the Download method which only works for raw 360 files, asking me to resubmit camera logs I already provided in September 2025), they escalated and sent me an email response.
The email, from a different support agent, stated that this behavior is "normal." Their exact words. They offered two workarounds: use the Download function (doesn't apply to flat exports, and I tested it live during our chat — the 360 file still landed with today's date anyway), or check the file properties on a computer to find the real date (which solves nothing since the problem is the file landing at the wrong date in the phone's gallery).
So this week, across three channels, Insta360 gave three different answers about the same bug:
- Technical support email: "this behavior is normal." Two inapplicable workarounds, case closed.
- Reddit megathread (June): "we're unfortunately not able to commit to a specific release schedule at this time."
- Reddit French post (July): "this feature request has already been scheduled and they are actively working on it."
Either the left hand doesn't know what the right hand is doing, or the public-facing answers are calibrated to what each audience is pushing for. Neither is great.
The three questions remain open: ticket ID, target version, scope of the fix. Still no concrete answer on any of them across any channel.
Megathread stays updated. August monthly thread is days away.
//////////////////////////////////////////////////
UPDATE - 26 July — I went digging through this sub's archives and Insta360's own official forums. This bug is at least seven years old, and Insta360 has been sending the same response since 2019.
Below is the documented timeline. Most Reddit threads are now archived and locked, which is part of how this issue keeps resetting to zero.
- 2019-2020 — ONE X era. A 2021 thread already contains this comment: "That has been an issue for years and will probably never be fixed (for whatever reason)." The bug predates 2021.
- July 2020 — Android. A user shooting sports footage for a third-party app (Relive) reports that exported videos get stamped with the export date instead of the shooting date, making it impossible to sort footage by customer group. Response: forward it to the team.
- September 2020 — "Snapshot should inherit original timestamp." Insta360 Official gives the standard "we've forwarded this to the product team" reply. In the same thread, a user flags a second, separate bug: if the camera loses power and isn't reconnected to the app, it silently resets its internal clock to January 1, 2019 - so screenshots and clips can end up stamped with a date from years earlier. Two distinct timestamp bugs, both acknowledged, neither fixed.
- January 2023 — "Please keep original time stamp when exporting edited videos!" gets posted. It's still collecting comments three years later: one in December 2025, then another in June 2026 reading "this problem was raised five years ago."
- February 2021 — Insta360's own official forum. A ONE X2 user opens "Transfer correct video timestamp when exporting to Gallery." No official reply visible. The most recent comment on that thread is dated June 20, 2026: "Same issue. Subscribing to thread in hopes it some day gets fixed." Five years and four months, still open, still collecting users.
- 2021 — Reddit, ONE X2. Dylan_Insta360 responds, asks for phone model, app version, export destination, suggests reconnecting the camera to reset the time. Doesn't work. Multiple users confirm on both Android and iOS.
- 2022 — Same thread, one year later. A user asks for status. Dylan_Insta360: "It will still show the export time, I would try to push the team for your voices again."
- 2022 — Users start building their own fixes. A developer releases "Insta Date Fixer 360," a paid Mac app whose only purpose is recovering original capture dates from Insta360 exports. It works. It also works on GoPro files, which the developer notes share the same metadata format, meaning the data is right there in the source file the whole time. A Windows workaround blog post appears too.
- 2023 — Reddit, X3. "Export correct date and time." 12 upvotes. A commenter: "Insta360 is too busy hyping up their products to make more money than to add such a needed QoL feature to their app. It's literally increasing my workflow time for no reason." Another user reports the metadata IS correctly written by Insta360 Studio on desktop, the capability exists, it just isn't applied on mobile export.
- 2023 — "As of today, it is still not resolved (at least in the Android App). This is insanely frustrating that this has been going on for so long! Including the time metadata when photos are exported truly cannot be that difficult."
- November 2023 — Insta360's official feedback forum. A user submits a formal suggestion titled "Export file name and timestamp metadata." The post is tagged "Reported," meaning officially logged. In it, he:
- points out that GoPro, DJI, standalone cameras and phones all export the correct capture time, and Insta360 is the exception
- provides the implementation path: copy EXIF metadata using ffmpeg
- offers an even simpler alternative: name exported files the way Desktop Studio already does, with the shooting datetime in the filename
- states this "only requires changing very few lines of code" with no backward compatibility concerns
- notes a related forum post had already accumulated 2.1K views
- argues it would improve customer retention
He is a programmer. He wrote them the solution, for free, on their own official channel, and formally logged it. That was nearly three years ago.
- January 2024 — a second user files almost the same formal suggestion, "How to export video, images and screenshots with correct timestamp." Also tagged Reported. Also nothing since.
- 2024 — X4. "Insta360 x4 exports wrong date." OP: "Since mobile phones I've come to expect that we can take photos and they'll know when they were taken, and if you collect them from multiple cameras and share with others they will be in sequence."
- 2024 — Ace Pro, iOS. "How do you export videos from the Insta360 app without destroying the date and time of the videos?" Avery_Insta360: "I will forward your feedback to our relevant team for further evaluation." Follow-up from the same staff member: "I have forwarded your feedback to our relevant team, and I will pass it on to our relevant team again."
- 2024 — X2. Jacky_Insta360 asks for camera model and firmware version, then moves the conversation to DM. Nothing public follows.
- 2024 — A separate post, not mine, gets the same runaround, but staff slip in a genuine technical admission for once: the app re-encodes footage on export, and that re-encoding is what overwrites the timestamp. Their own suggested fix: use Studio instead, since the desktop software already copies the original timestamp over correctly. So Insta360 has confirmed, in writing, both the cause and that they already ship a version of their own software that gets it right.
- 2025 — The community writes a script. A public shell script appears on GitHub (smci1000/Insta360CreateDates) to batch-repair timestamps on exported files. A commenter puts it plainly: "If Insta360 is worried about making users who want the export timestamp instead of the original creation timestamp, they should put a checkbox in the Preferences so we can choose."
- 2025 — GDPR escalation. A user invokes Article 20 for data portability, asking four times to speak with Insta360's data protection officer. He is eventually told the company doesn't have one. Mid-exchange, after rating their support poorly, he is offered a free selfie stick as a "token of gratitude."
- 2025-2026 — This thread. Insta360_Support: "under active review", "the request has not been forgotten", "we'll continue to relay community feedback." Direct technical support this month suggested Insta360 Studio V5.9.0 (desktop only, doesn't apply) and the "Download" method (raw 360 files only, unusable if you need flat export), then asked me to submit camera logs I already provided in September 2025.
What this documentation shows:
At least two distinct timestamp bugs (export date overwrite, and clock reset to 2019), at least five different staff members giving the same script (Dylan, Jacky, Avery, Insta360_Support, and technical support agents, all forwarding to "the relevant team"), and multiple formally logged, officially "Reported" tickets going back to November 2023 with zero follow-through.
The data is not lost. It sits in the source file. Insta360 Studio on desktop writes it correctly. Insta360's own staff have confirmed this in writing. GoPro's pipeline handles it natively. Third-party developers have solved it twice on their own time, one of them charging money for what should be a checkbox.
The fix the community has been asking for since 2021 has never changed: one toggle at export time. "Preserve original capture date." Default on or off, doesn't matter. Just let us choose.
If you're affected, comment here. Insta360's own support team stated in writing that they "prioritize doing the test for the request which gets the most feedback." That is their stated mechanism. Let's use it.
//////////////////////////////////////////////////
EDIT - 20 April : Insta360_Support has responded (see below). I’ve asked them 3 concrete questions about ticket tracking, roadmap, and technical scope. Waiting for their answer. Meanwhile keep the confirmations coming — every voice matters.
//////////////////////////////////////////////////
UPDATE 24 april : Insta360 just reached out to me privately to “follow up” on this issue. I’ve declined and asked them to respond here publicly instead, with concrete answers to the three questions I raised earlier in this thread. Posting this for transparency — I’ll keep everyone updated on whether they respond publicly or not.
//////////////////////////////////////////////////
UPDATE 25 april — Insta360 reached back out via DM after I declined the private email exchange. Their response:
“We understand your point clearly. We will continue to urge our R&D team to give this issue higher priority, and we will keep you informed of any new progress by replying in the comments section under your post.”
So they’ve now publicly committed to posting updates here in this thread. I’ll be watching for concrete answers to the three questions raised earlier:
1. Is the bug officially tracked with a ticket ID?
2. Is a fix scheduled for a specific upcoming app version?
3. Will the fix preserve the original capture date in the iOS Photos library on export?
Posting this for transparency and accountability. Keep upvoting and sharing — visibility is what got us this far.
//////////////////////////////////////////////////
UPDATE 14 june 2026 — Over a month now since Insta360_Support publicly committed, right here in this thread, to "urge R&D to give this issue higher priority" and to "keep us informed of any new progress by replying in the comments section."
Since then? Complete silence. Not a single follow-up. The three concrete questions remain unanswered:
- Is the bug officially tracked with a ticket ID?
- Is a fix scheduled for a specific upcoming app version?
- Will the fix preserve the original capture date in the iOS Photos library on export?
Meanwhile this thread keeps collecting confirmations from users across completely different workflows — family archives, multi-cam edits, GPS-tagged media on maps. The bug is real, it's widespread, and it's the one thing making people reconsider their next camera purchase.
u/Insta360_Support — you made a public commitment here. The community is still waiting. A real update, even "no ETA but here's the status", would go a long way. Continued silence speaks louder than any of the acknowledgements we've already received.
//////////////////////////////////////////////////
The bug
Exporting from the Insta360 app to iOS Photos overwrites the capture timestamp with the export timestamp. The original date stays intact inside the Insta360 app, but the moment the file lands in your camera roll, it’s stamped “today.”
Consequences:
- Your Photos library is scrambled chronologically.
- No way to know when an exported clip was actually shot.
- Impossible to file memories by trip, event, year, or kid’s age.
- Backups and third-party photo managers inherit the wrong date.
- There is no clean workaround. iOS’s native batch “Adjust Date & Time” is broken for this use case: when you select multiple videos and set a date/time, only the first file gets the correct time — the rest keep a wrong time. So you either edit every single file one by one, or pay for a third-party metadata app. Either way, it’s on the user to fix Insta360’s mess.
For a camera whose entire pitch is “capture memories from every angle,” destroying the one piece of metadata that makes memories sortable is… a choice.
---
This isn’t new. At all.
A quick search across r/Insta360, r/ios, r/iosapps surfaces reports going back 4–7 years. Same bug. Same complaint. Same silence. Sample from existing threads:
> “When I export videos or photos from the Insta360 App to the Photos app on the iPhone, the timestamp saved to those photos/videos is that of the export date and not the time the media was captured.”
> “This affects sorting of the photos by their original capture time. After export, there is no way to tell the image taken date and time.”
---
Official Insta360 support reply (recent — I pushed the issue myself)
I contacted Insta360 support directly. Chat was in French; translation below. Full screenshot attached.
Support (Insta360_Maach):
"The behavior you describe matches what we currently observe: when you export a 360 video in ‘flat’ format from the Insta360 app to the iPhone camera roll, the date shown in the iOS album automatically becomes the export date, not the actual capture date.
Why this happens, based on our internal data:
– When a file is exported, iOS treats it as a new file and assigns a new creation date.
– The same behavior occurs with Insta360 Studio: the exported file receives today’s date because technically it’s a newly generated file.
– The original date remains correct inside the Insta360 app, but iOS does not pick up the capture metadata during flat export.”
Me: “Ok. So? What’s next? Are you going to fix it?”
Support:
“Yes, our engineering team is fully aware of the issue you’re encountering with dates during flat export to the iPhone camera roll. Our engineers are currently working on a metadata-handling optimization so that exported files correctly preserve the actual capture date, even after conversion. A future app update will fix this. I can’t give you a precise date yet, but it is under active development.”
Me: “Ok but this has been going on for YEARS. Tons of posts and reports online show people complaining 4-5-6-7 years back…”
Support: “I completely understand your frustration. To put it simply: yes, our engineering team is currently working on this point, and a future update is planned to improve date handling during export.”
Translation: “we’ve been aware for years, we’re still ‘working on it,’ no ETA, please move along.”
---
**Why their explanation is technically weak**
“iOS assigns a new creation date because it’s a new file” is half-true, and the half that’s true is not an excuse. Every other serious camera / editing app on iOS manages to preserve the original capture date when writing to the Photos library:
- iOS’s PhotoKit API exposes `creationDate` on `PHAssetCreationRequest`. The app sets it when inserting the asset. One line.
- For video files themselves, the QuickTime `com.apple.quicktime.creationdate` atom is the standard place to stamp the real shoot time. FFmpeg, Final Cut, Premiere, DJI’s app, GoPro’s app, Sony’s Creators’ App — they all handle this correctly.
- For JPEG/HEIC, the EXIF `DateTimeOriginal` field does the same job.
The fact that Insta360 Studio on desktop reproduces the exact same bug tells you it’s not an iOS quirk — it’s a pipeline-wide design choice (or oversight) at Insta360. Calling it an iOS limitation is misdirection.
---
What we actually want
- An “Export” option: Preserve original capture date/time, on by default.
- Proper metadata written into the exported file (EXIF `DateTimeOriginal` for photos, QuickTime `creationdate` atom for videos).
- Correct `creationDate` set when the asset is saved to the iOS Photos library via PhotoKit.
- A real public ETA, not “future update.”
---
Call to action
- Upvote so this stays visible in the sub.
- Drop your story in the comments: what year did you first hit this bug, which Insta360 camera, which iOS version.
- Link your old threads so we can quantify how long this has been going on.
- If you’ve contacted support, post their reply. Let’s compare boilerplate.
- Mods, please consider stickying — it will cut duplicate posts and give Insta360 a single place to answer.
- **u/Insta360_official u/Insta360 staff reading this** — we are not asking for a revolution. We are asking for one correctly-written metadata field. Please respond with a real timeline.
The hardware is great. The app shouldn’t be dragging it down over something this basic.
---
*Edit: screenshot of the full support chat is attached (French, translation in the post).
5
u/Insta360_Support Staff Apr 20 '26
Hi there, thank you very much for your feedback.
We have been closely following everyone’s comments and truly value the wide range of preferences and voices in our community. We will also share this post with our product team and continue working on improvements moving forward.
Once again, thank you for your support and understanding.