
ExifTool's QuickTimeUTC setting changes how supported integer-based QuickTime date fields are interpreted on reading. It does not establish that the camera stored the correct time. Compare the two interpretations against a trustworthy event reference before deciding whether any timestamp needs rewriting.
Why a time-zone-sized difference appears
The ExifTool QuickTime tag documentation explains the conflict: the specification calls for UTC in integer date fields, but cameras sometimes store local time there. ExifTool therefore does not assume UTC by default. When QuickTimeUTC is enabled, it treats those values as UTC and converts them to the computer's local time on extraction.
This is a metadata interpretation issue. It is different from shifting a sequence because the camera clock itself was wrong. The same file can consequently produce different displayed times without a write operation.
Compare two read-only reports
Use the same local movie for both requests:
exiftool -a -G1 -s -time:all sample.mov
exiftool -api QuickTimeUTC=1 -a -G1 -s -time:all sample.mov
Neither command assigns a new value. Record the computer's current time zone alongside the output so another person can understand the comparison.
Keep the group identifiers. Movie, track, media, string-based capture tags and filesystem dates can describe different things. Do not compare whichever two lines happen to have similar names and call the difference a clock defect.
Use independent evidence to choose an interpretation
Imagine a clip filmed during a documented appointment at 14:00 local time. If one interpretation agrees with that appointment and another differs by the applicable zone offset, that is a useful clue. It is not a measured result for your camera; daylight-saving rules, an incorrect camera setting or an unreliable appointment note can still invalidate the inference.
Check another clip from the same device and period if one is available. Do not combine unrelated cameras into one correction rule. A correctly interpreted integer timestamp and a contradictory string tag should remain two recorded findings until the intended authority is established.
Capture-time sequence correction solves a different task: applying a justified clock adjustment. Do not substitute it for deciding whether the stored number was UTC in the first place.
A reading option is not a repair command
Avoid adding a blanket offset merely to make the default ExifTool display resemble a player. First document which field that player uses and which interpretation is justified. Changing every date can damage otherwise correct creation, modification or filesystem records.
The acceptance artifact for this investigation is a small field table: original grouped value, value with the UTC interpretation, computer time zone and corroborating event evidence. Mark unresolved fields as unresolved.
When the eventual goal is matching a tracklog, GPS-to-photo time matching additionally needs the track's time basis and the correct capture event. A visually plausible hour on screen is insufficient to justify a location match.
Related tasks
- Correct a Camera Clock Offset in Lightroom Classic
- Lightroom GPX Auto-Tagging Misses Photos: Check the Tracklog Time Offset
Sources and scope
- QuickTime Tags: Integer QuickTime timestamps should be UTC, but some cameras write local values. QuickTimeUTC changes interpretation; string date tags have different timezone behavior.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai). Commands and acceptance procedures are proposed examples, not reported hands-on tests. Official ExifTool documentation was readable through search-indexed page text; a direct application-documentation fetch returned HTTP 403. Historical official-forum examples, where cited, demonstrate specific questions rather than current demand frequency. ExifTool version and file-format support must be checked on the receiving system.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.