Applies to Final Cut Pro 12 on macOS Ventura through macOS 27
The short answer: for movies, Final Cut Pro reads exactly one embedded date, the Apple
creation-date key inside the QuickTime container (com.apple.quicktime.creationdate), and only when
that date carries a time-zone offset. If the key is missing or has no offset, the clip gets the
file’s creation date from the Finder. For JPEGs it reads the IPTC Date Created first and the EXIF
date second. Every other date a metadata tool shows you is ignored. To fix a wrong Content Created
date, write the right value into those fields, then import the clip, and the browser will file it
where it belongs.
A disclosure: I’m the developer of A Better Finder Attributes, a paid utility that writes these dates in batches. I ran the test below because customers kept asking why a date they had corrected “did not show up in Final Cut”. The free routes come first.
Three boundary checks, because three different guides serve three different goals:
- Your clips show the wrong date inside Final Cut Pro and you want them sorted and grouped by when they were shot → this guide.
- Your files show the wrong date in the Finder and Final Cut Pro is not involved → change a file’s Created or Modified date.
- Your photos land on the wrong day in Apple Photos → the sibling guide, why Apple Photos shows the wrong date; Photos reads a different set of fields.
Why the date in Final Cut Pro is wrong
Final Cut Pro’s browser groups and sorts clips by a field called Content Created. That field is filled in once, at import, from metadata inside the media file. When it is wrong, it is nearly always for one of these reasons:
- The camera never wrote the date Final Cut Pro looks for. Many cameras, screen recorders and older phones write the standard QuickTime header dates but not the Apple-specific key. Final Cut Pro then falls back to the file’s creation date, which is the moment the file was copied to your Mac, not the moment it was shot.
- The file was copied, downloaded or restored. Copying through a cloud service, AirDrop or a backup restore gives the file a fresh creation date. If the clip has no embedded key, that fresh date is what Final Cut Pro shows.
- A tool “fixed” the date in the wrong field. Rewriting the QuickTime header’s creation time,
the
©daycontent-created tag, or the XMP dates inside a movie changes nothing in Final Cut Pro. Neither does writing the right key without a time-zone offset: Final Cut Pro throws that value away. - A stale IPTC date on a JPEG. Stills exported from Lightroom, Photoshop or Capture One usually carry an IPTC Date Created. Final Cut Pro ranks it above the EXIF date, so correcting only the EXIF “date taken” leaves the still where it was.
- The camera clock was wrong. The date is embedded correctly, it is just the wrong date. Same fix, different starting value.
Which date Final Cut Pro actually reads
I could not find this documented anywhere, so I measured it: about sixty test files, each with every date field set to a different, recognisable year, imported into Final Cut Pro 12.3 on macOS 27, and the Content Created column read back after import. The method is at the end of this page; this is what it showed.
Movies (.mov and .mp4). One field, with one condition:
com.apple.quicktime.creationdatein the movie’s Apple metadata keys, only if the value has a UTC offset such as+02:00orZ. It is displayed converted to your Mac’s local time.- Otherwise the file-system creation date, as shown in the Finder’s Get Info.
That is the whole chain. Final Cut Pro ignores the movie header’s creation and modification times
(mvhd), the track and media header times (tkhd, mdhd), the ©day content-created tag in both
of its possible locations, any XMP dates embedded in the movie, and a key written without an offset.
A file’s modification date is never used.
JPEG stills, in priority order:
- IPTC Date Created (with Time Created)
- EXIF
DateTimeOriginal, the “date taken” - XMP
photoshop:DateCreated - XMP
exif:DateTimeOriginal - the file-system creation date
EXIF CreateDate (the “digitized” date), EXIF ModifyDate, IPTC Digital Creation Date and the XMP
xmp:CreateDate, ModifyDate and MetadataDate fields are ignored.
PNG stills follow the JPEG chain minus the IPTC entries: EXIF DateTimeOriginal, then the two
XMP fields, then the file’s creation date. The PNG-native tEXt “Creation Time” keyword and the
tIME chunk are ignored.
Time zones. For movies the offset on the Apple key is honoured and required. For stills, EXIF
OffsetTimeOriginal is honoured (and applied even when the IPTC date wins); offsets inside IPTC
Time Created or on XMP dates are dropped. A still with no offset at all is treated as local
wall-clock time and shown unchanged. Final Cut Pro always displays the result in the local time of
the Mac it runs on, which is one reason it and Apple Photos can show different times for the same,
correctly dated file. Photos keeps the camera’s time zone; Final Cut Pro converts to yours.
Why the Finder and Final Cut Pro disagree
The Finder and Spotlight never read the Apple creation-date key. For a movie they show the file-system creation date, full stop. So a clip with a perfectly good embedded date shows the recording date in Final Cut Pro and the copy date in the Finder, and a clip without the key shows the copy date in both. Neither is a bug. They are two different dates, and the fix that makes them agree is to set both: the embedded key for Final Cut Pro and the file creation date for the Finder. The file dates guide explains the file-system half in detail.
One trap that follows from this: the Media Import window lies. Its Content Created column shows the file-system creation date for every file, even ones with a correct Apple key. Only the event browser, after import, reads the embedded date. Judge results in the browser’s list view (View ▸ Browser ▸ as List, or ⌥⌘2), Content Created column, never in the import window.
Free route 1: change the date inside Final Cut Pro
Select the clips in the browser and choose Modify ▸ Adjust Content Created Date and Time…. Final Cut Pro rewrites the date in its library and re-sorts the clips.
The honest limit: this edits the library, not the file. Import the same clip into another library, hand the file to a colleague, or archive it, and the wrong date comes back. For a one-off clip in a one-off project it is the quickest fix there is. For a card full of footage that will outlive this project, fix the files.
Free route 2: ExifTool
The free command-line ExifTool can write the one field Final Cut Pro reads.
The tag it calls CreationDate is the Apple key; ExifTool appends your Mac’s UTC offset for that
date, which is exactly what Final Cut Pro requires:
# one clip, shot on 15 June 2024 at 10:30 local time
exiftool "-QuickTime:CreationDate=2024:06:15 10:30:00" clip.mov
# check what Final Cut Pro will see
exiftool -a -G1 -time:all clip.mov | grep -E "Keys|File Creation"
A correct file shows [Keys] Creation Date : 2024:06:15 10:30:00+02:00, offset included. For JPEGs,
set the EXIF date and the IPTC date, or clear the IPTC date, otherwise the stale IPTC value keeps
winning:
exiftool "-DateTimeOriginal=2024:06:15 10:30:00" "-IPTC:DateCreated=2024:06:15" \
"-IPTC:TimeCreated=10:30:00" still.jpg
The usual command-line caveats apply: no preview, and a typo in a date or a wrong sign in a shift recipe moves a whole folder the wrong way in a blink. The file’s creation date does not follow automatically, so the Finder will still disagree until you set that too. And ExifTool rewrites the container, so work on copies of anything irreplaceable.
The batch tool: A Better Finder Attributes
Setting embedded dates for a whole shoot is what A Better Finder Attributes is for. Since version 7.50 its content-creation actions write the Apple creation-date key, with the offset, on every movie write, and update a JPEG’s IPTC Date Created alongside the EXIF date, so the defaults produce files that Final Cut Pro (and Apple Photos) file correctly. The workflow that needs the fewest decisions:
- Drop the clips and stills onto the window.
- Choose Advanced date manipulation in the Action: popup.
- Set Use: to Specific date and enter the date and time the footage was shot. (Or pick one of
the Existing … sources to copy a date the file already carries elsewhere, or the file-name mode
for clips named like
2024-06-15_1030_clip.mov.) - Under Overwrite:, tick File creation date. Leave For Images: at Set DateTimeOriginal and For Movies: at Set Content Creation & Media Create Date, the defaults.
- Check the preview: each file shows its current date and, next to it, the date it will get. Then run.
- Import into Final Cut Pro, or re-import clips that were already in the library.
Step 4 is the one that makes the Finder, Spotlight and Final Cut Pro agree. It also means the clip still lands on the right day if it later passes through a tool that strips metadata, because the Finder date is Final Cut Pro’s fallback.
For a shoot whose camera clock was simply off, the Adjust EXIF content creation timestamp action shifts every file by the same number of hours or days instead, which keeps the intervals between shots intact. There is no separate “camera time zone” control: the time you enter is local time on your Mac for that date, and the offset written into the file is that zone’s offset on that date, daylight saving included.

The whole fix in one action: the embedded key for Final Cut Pro, the file creation date for the Finder, and a preview of both before anything is written.

The same clips after import, grouped under the corrected Content Created date in the browser’s list view.
It’s version 7, US$29.95 / €29.95 as a one-time purchase, with a free trial to check it against your camera’s files.
On version 7.49 and earlier. The default movie mode wrote the ©day tag and the media header,
neither of which Final Cut Pro reads. Set For Movies: to Set QuickTime Creation Date (or Use
Apple Photos Brute Force Mode) instead, and tick File creation date so the fallback is right too.
For JPEGs with a stale IPTC date, run Remove content creation date with the IPTC fields ticked
first, then set the EXIF date. Updating is the simpler answer.
Check your work
Import into a throwaway event, switch the browser to list view, read the Content Created column. On the command line, for a movie:
exiftool -a -G1 -time:all clip.mov | grep -E "Keys|File Creation"
You want a [Keys] Creation Date line with an offset at the end, and the same value under File
Creation Date if you set the file date too. For a still, exiftool -a -G1 -time:all still.jpg
should show the intended date in DateTimeOriginal and, if present, in the IPTC Date Created
line.
The tricky cases
- Clips already in a library. Final Cut Pro reads the date at import and never again. Fix the file, then re-import it (the fixed file is treated as new media), or use Adjust Content Created Date and Time on the clips already there.
- Stills from Lightroom, Photoshop or Capture One. They carry an IPTC Date Created that outranks the EXIF date. Update both or clear the IPTC one; a tool that only touches EXIF will not move the still.
- Footage shot abroad. A phone clip carries the offset of the place it was shot; Final Cut Pro shows it converted to your Mac’s zone, so an 09:00 clip from a trip two zones east shows as 07:00 at home. That is correct behaviour, not a wrong date. If you would rather see the local time of the shoot, shift the clips by the zone difference.
- Camera sidecar XML. Sony, Canon and Panasonic cameras write an XML file next to each clip. My test did not cover them, and Final Cut Pro may take the date from the sidecar before it looks at the media file. Keep or delete sidecars consistently across a shoot.
- Modification date earlier than creation date. macOS pulls the creation date back to match if you set a modification date before it. If you set both, set them in that order, or let a tool that knows the rule handle it.
Common pitfalls
- Trusting the Media Import window. It shows Finder dates. Check the browser after import.
- Writing the key without an offset.
2024-06-15T10:30:00with nothing after it is discarded; the clip falls back to the Finder date and looks “unfixed”. - Fixing the QuickTime header instead of the key. Many tools rewrite
mvhdand call it the creation date. Final Cut Pro does not look there. - Fixing the embedded date and forgetting the file date. Final Cut Pro is happy, the Finder still sorts the clip under the copy date. Set both in one pass.
- Editing originals without a backup. Metadata edits rewrite the container. Work on copies of anything you cannot re-shoot.
FAQ
Why does Final Cut Pro show the wrong Content Created date? Because the clip has no Apple creation-date key (or one without a time-zone offset), so Final Cut Pro falls back to the file’s creation date, which is usually the date the file was copied to your Mac. Write the key with an offset and the clip moves to the right day.
How do I change the Content Created date in Final Cut Pro? Inside the app: Modify ▸ Adjust
Content Created Date and Time…, which changes the library only. In the file itself: ExifTool’s
QuickTime:CreationDate tag, or A Better Finder Attributes’ Advanced date manipulation with File
creation date ticked, then import or re-import.
Does changing the file’s date in the Finder change it in Final Cut Pro? Only for clips that have no embedded key: those use the Finder’s creation date as a fallback. Clips with an embedded key ignore the Finder date entirely.
Why do the Finder and Final Cut Pro show different dates for the same clip? The Finder shows the file-system creation date and never reads the embedded key; Final Cut Pro reads the key and ignores the Finder date when the key exists. Set both to the same value and they agree.
Why does the date show one hour off? Time zones. The key stores an offset and Final Cut Pro converts to your Mac’s local time; a clip shot in another zone, or a still whose EXIF offset differs from your zone, shows converted. If the hour is wrong for a clip shot at home, the camera clock or its zone setting was wrong: shift the batch.
Does this apply to Final Cut Pro on the Mac only? The test was run on Final Cut Pro 12.3 on the Mac. Apple has changed date handling between versions before; if a future release behaves differently, this page will be updated.
How the test was done
About sixty files were generated with no metadata at all (a 320×240 H.264 movie from AVAssetWriter,
JPEGs and PNGs from macOS’s own image writer), then stamped with ExifTool so that every date field
carried a different, recognisable year, 2001 through 2019, always at noon. File-system creation and
modification dates were set to 2012 and 2013 where relevant. The files were imported into a
throwaway library in Final Cut Pro 12.3 on macOS 27 and the Content Created column read in the
browser’s list view. A displayed year identifies the winning field directly; an hour shift reveals
time-zone handling. One control per format was left untouched. Real iPhone footage was checked
against the same read-out. Results for the movie header, track header, media header, ©day in both
locations and all XMP dates were negative in every combination. The priority orders above were
established with two-field knockout files, not inferred.
Frank Reiff is the developer of A Better Finder Attributes and A Better Finder Rename, Mac file-management utilities in continuous development since 1996. Related: why Apple Photos shows the wrong date on imported photos and videos, how to change a file’s Created or Modified date on a Mac and how to change the date a photo was taken, or get in touch with a date problem this guide doesn’t cover.