What To Do When You’re Done Editing an Apple Final Cut Pro Project

Posted on by Larry

This tutorial was suggested by Patrick Flaherty, who wrote:

Would you please explain the steps to take when you are finished with a FCP editing project – what to save and what to delete?

Sure.

First, let’s set the scene. All your editing is complete, the final project is exported, and the client has signed off on the project. Now what?

A Final Cut project consists of multiple potential elements:

By default, the following elements are contained inside the library:

Whoa! Suddenly there’s a lot more to think about than simply deciding what to do with the Library file.

NOTE: While media can be stored inside the library, it is most often best stored outside of it. Also, archiving and sending files to clients is the main reason I don’t store images in Photos or music or sound effects in the Music folder. Elements in Photos or Music are way too hard to export for archiving. I always store all media files – audio, video, stills and motion graphics – in their own folders outside the library.

It seems to me that there are four things we can do with any FCP project:

  1. Do nothing.
  2. Delete the project from your system.
  3. Return the entire project to the client and delete it from your system.
  4. Archive the project on your system for the future.

CREATE AN XML BACKUP FILE

IMPORTANT: Before you do anything else, create an XML version of your finished project.

NOTE: Always use the latest version of XML displayed in this dialog for archiving.

Why is this necessary? Because FCP libraries use a proprietary format that only Apple knows. No other application can open an FCP library. However, LOTS of programs can open that XML file. If you ever need to access an older FCP project, you can do so if you created an XML file. You most often can’t if you don’t.

Creating an XML file is a big deal! It is fast, it doesn’t take much storage space, and it can save your tail in the future. Get in the habit of creating one for every completed project.

NOTE: An XML files does not contain media, it only contains the instructions on how that media was edited. Media still needs to be handled separately.

A NOTE ON STORAGE

While it is far too late at the end of a project, if you know you need to either delete, archive or return a project, it will make your life MUCH easier to create a single folder – outside of Final Cut – into which you store media, audio, graphics, and work files for that project. Use as many subfolders inside as you want. The key, though, is to have all the media elements related to one project stored in one place. The library can be stored separately from this folder, because it is always easy to find.

Putting all show elements in this single, organized entity makes backups, archiving and transferring as easy as dragging a folder from Point A to Point B.

If you reorganize media after a project is over, you’ll break all the links between FCP and the media, which means everything in your project will need to be relinked. This, you’ll quickly discover, is a MAJOR pain in the posterior.

NOTE: After posting this, Patrick commented: “Editors must understand that how you organize a project in the beginning will affect how you finish.” Organizing where to store media and project elements before you start is really important!

OPTION 1: DO NOTHING

This tends to be the preferred choice. The end of any significant project is exhausting. Nothing is easier than saying: “I’ll clean this up tomorrow.” Except that tomorrow brings a new job and, well, you get distracted.

There’s no harm in this approach – provided you created an XML file. If not, go do so now.
As long as you have the storage room, letting things be is fine.

Really.

OPTION 2: DELETE THE PROJECT FROM YOUR SYSTEM

Frankly, this is what I do with all the demo files I create for my webinars and tutorials. Once the webinar is done, or the tutorial written, I don’t need it any more. So I delete it. (Though I do keep all the media for reuse.)

Let’s say you want to delete everything associated with a project – except for software and plug-ins – here’s what you need to delete and where it’s stored.

Element Where It’s Stored
Library On your hard disk
Library Backups [Home Directory] > Movies > Final Cut Backups, unless moved by you to a different location.
Media On your hard disk – or – inside the Library file.
Motion Content [Home Directory] > Movies > Motion Templates – or – inside the Library file.
Cache, render, analysis & other work files Inside the Library file, unless moved by you to a different location.

Generally, I suggest you delete the Library file, related media and the backups. I would generally leave any motion graphic templates and all plug-ins for use in future projects.

Retaining the XML file is a good idea if you are keeping the media, but, if you trash the media, you can delete the XML file as well.

A few minutes clean-up and you’re done.

NOTE: You can delete Final Cut backups at any time – I just picked up 3 GB of space by trashing backup files of long-ago projects that I hadn’t bothered to delete before today. Just be sure to quit FCP before deleting backup files.

OPTION 3: RETURNING PROJECTS TO THE CLIENT

Before returning files to the client, you can safely delete work files that Final Cut created during editing. Doing so will save gigabytes of storage space. These include:

To delete these:

Once these files are deleted, gather the following files for your client:

You don’t need to return any FCP backup, render, proxy, or cache files.

OPTION 4: ARCHIVING PROJECTS

Just as when sending files back to the client, when you archive a project you can delete render, optimized, proxy and backup files as I just described.

Here, creating an XML file is critical, because there is no knowing how long Apple will support older FCP files themselves. As examples, look at FCP 7 and FCP X 10.0. Neither of these project files can be opened today. However, XML files created by both of them CAN be opened in a variety of software, including Final Cut.

Again, you’ll want to archive:

You don’t need to save any FCP backup, render, proxy or cache files.

What makes archiving tricky – and there are no good answers here – is the on-going evolution of operating systems and software. Opening a project a year from now is fairly assured. Opening it ten years from now is not.

Adobe has done a better job of supporting older formats than Apple has. Photoshop is a good example of supporting older files. FCP 7 is not. 3rd-party plugins are also an issue; it’s not unusual for a developer to lose interest in developing a plug-in that was essential for your current project.

Make good notes about the tools you used for a project and include the name and version of:

I think it is a safe assumption that you’ll be able to open both the XML file and media in ten years. But you most likely won’t be able to open any programs or plug-ins. Factor that into your planning.

SUMMARY

The process of wrapping up any Final Cut Pro project is fairly simple, especially if you think about where to store media and project elements before you start editing.

The REAL challenge is planning for technology obsolescence in the future. Here, your best protection is storing media separate from the library and exporting an XML file of the completed project. That, and good notes on what you did, will protect you when you need to revisit this project in the future.


Bookmark the permalink.

38 Responses to What To Do When You’re Done Editing an Apple Final Cut Pro Project

Newer Comments →
  1. First of all, thank you, Larry. For this and for all the tutorials you have shared along the years. I am truly grateful for your guidance and wisdom. It has been invaluable.

    Now, with regards to XML’s. I have found recently, that on occasion when I import an XML (and it can be a fairly recent one, from a year ago for instance), I lose all of my titles. The actual text for the title information is there in the text window, but in the viewer and the rest of the settings are the defaults. This leads to my having to rebuild the titles which is very annoying, and caused me to lose faith in XML’s. Have you encountered this before? I did check to make sure that the computer I was running had all the appropriate font files, and it does. I’m running on all updated software. Thoughts on how to avoid this or what to do when it happens? Thanks!

    • Larry says:

      Mark:

      Titles are a special case because they are text, formatting and, often, an effect applied to that text. While XML easily supports both the text and format, it may have problems with animation applied to the title.

      Larry

  2. This is great Larry, thank you. Have been looking for this as well!

  3. Alan Nesbitt says:

    Thank you Larry, this is just what I need to cover the Archive process. Had used XML during transition from FCP7 to X years ago but you have helped me real realise its importance today. I have been using the method you suggested to clear render and optimised files but unless I switch off auto rendering in Preferences it all re- renders. again when I reopen FCP. Couldn’t understand why file sizes went down and then back up again. Is there a way round this? Thanks again for the help that you give.
    Regards
    Alan Nesbitt

    • Larry says:

      Alan:

      Render files are necessary and required for editing. If they are missing, FCP MUST recreate them. Don’t bother deleting them until the project is complete.

      Larry

  4. Kelvin Jones says:

    Larry, thank you so very much for all these articles. They are an invaluable education and I recommend them to all and sundry! I should like to recommend Final Cut Library Manager as a superbly easy way to keep my storage managed, at least where I keep all media in the library itself. I have pretty simple requirements and this keeps it that way. Thanks again for all you do. Cheers, Kelvin

  5. Bud Kuenzli says:

    Fantastic explanation as always and as always. I do think that the advice to keep media outside of the library is dependent on how one uses media. In my case, I might go out and film a family event, return and make a video of our weekend and share it with family. I have no real use for the media outside of that event. I have a friend that does similarly. I keep my media in the library. He keeps his outside and he is forever buying new larger hard drives for his ever expanding needs as he buys new drones and begin shooting raw, etc etc. As you might guess, he is forever breaking links and spending hours trying to relink his files. I go years without that problem. For somebody that uses and shares media in a variety of projects I entirely agree that keeping the media files out of the library makes good sense and I also believe for many of us keeping them inside the library is the smart money. Thanks for the sharing of your experience and wisdom.

    • Larry says:

      Bud:

      Thanks for writing.

      One clarification, if I might. Storing media inside the library does not reduce your storage requirements. Media takes the same amount of space either in or out of the library.

      However, you are correct. If you are the only one accessing the media and you are not sharing it between libraries, storing it inside the library makes life a lot simpler. I also recommend storing media in the library for new editors, because it prevents – as you describe – dealing with broken links.

      Thanks for sharing your thoughts.

      Larry

  6. XML Back ups is a great idea. I use them to go between apps a lot. Davinci, Adobe etc. There are 3rd party apps for making FCP XML compatible with others and vice versa.
    Because I do this I do my titles in Photoshop and After Effects. This way I don’t have title problems as they are rendered as a graphic or movie and will work in all apps.

    • Larry says:

      Alan:

      XML is the only way to move projects from any NLE to another NLE or audio edit or, um, anything, actually. They are really, really useful.

      I also agree that creating graphics in Photoshop, or stand-alone movies in Motion or After Effects solves a lot of the “future-proofing” of your projects.

      Larry

  7. john-claude says:

    Thank you for a great article

    Doing video purely for myself, (mainly travels) I burn my edited projects to Blu Ray and DVD discs and view them via a HD projector on a decent size screen.

    I have also archived the original non-edited materials to “archives”, being aware of the limitations .

    Cheers

    • Larry says:

      John-Claude:

      Burning projects to DVD or Blu-ray is a good plan – provided your assets fit. Its definitely the least expensive option for archiving.

      Larry

  8. Scott Newell says:

    Thanks for raising awareness of how important it is to choose one of these options when you’re finished with a project. All good suggestions. I used to archive projects on LTO tapes but it’s an expensive system. And you still have to choose in what form you are going to archive the material.

    Larry, your thoughtful, methodical approach is especially useful for anyone who edits on a regular basis.

  9. Thanks Larry for this intelligent breakdown of a process that is typically fraught with anxiety and a bit of guesswork. Have you written a similar guide to coping with the aftermath of Adobe Premiere Pro projects? If not, please consider adding that to your excellent library of tutorials.

  10. Tony says:

    Hello everybody,
    I used the XML method on a multicam project, where the original files were left on a separate disk and the method WORKED perfectly (even when I deleted the original library). The multicam file is part of the project and therefore is included in the XML somehow. I could not understand how is this possible?

Newer Comments →

Leave a Reply

Your email address will not be published. Required fields are marked *

Larry Recommends:

FCPX Complete

NEW & Updated!

Edit smarter with Larry’s latest training, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!

JOIN NOW

Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.