Future-Proof Media Projects: Export XML Files From Premiere or Final Cut [u]

Posted on by Larry

[Updated March 28, 2021, with a new intro.]

For long-term archiving of any media project, I strongly recommend you export an XML version of every project you want to save – regardless of whether you use Adobe Premiere Pro or Apple Final Cut Pro.

Project files are proprietary, XML files are designed for transfer and archiving. Protect yourself.


One of the big, painful, lessons we learned with the demise of Final Cut Pro 7 was that it stored our edits in a proprietary format. Only FCP 7 could open FCP 7 project files. Once FCP 7 stopped working, we lost access to ALL our old edits. Not the media, but the edit.

However, if we had simply exported our FCP 7 projects as XML, we could access them today via Premiere or DaVinci Resolve or today’s Final Cut Pro.

NOTE: As another example, Final Cut Pro X 10.0 projects are no longer readable by today’s Final Cut. But they would be if we had exported them as an XML file.

The key point I’m making is that, regardless of the NLE we use, it is essential that we preserve our media and edits for the future. And that means exporting a finished project as an XML file, as well as saving the original project file.

XML files are designed for transferring files and data between applications. These text files are quite small, and readable by a wide variety of applications. This is because XML files do NOT contain media – they simply contain a “pointer” to your media. This is the path and file name of where your media is stored. So, exporting an XML file does not preserve your media, it only points to it.

If you open an XML file in the same application that created it, virtually all your project data should be safe. If you are moving XML files between applications from different developers, media files, edits and dissolve transitions, for example, safely transfer while most titles and effects do not.

Always archive your projects. The fastest and best way to open a project is to open the native project file. This preserves everything. But, for protection, also archive an XML of the same project.

NOTE: Keep in mind – because it’s important – that because XML does NOT contain media, you will need to archive media files separately.



Here’s a typical project in FCP; though short, this can easily illustrate the export process. It contains video and audio clips, transitions, titles and captions.

An XML (eXtensible Markup Language) file contains pointers to all clips, but not the actual media, as well as settings for just about everything in the project file.

Select the project in either the Timeline or the Browser, then choose File > Export XML. In the resulting dialog, give the XML file a name and storage location. Then, click OK.

NOTE: Be sure to always pick the latest version of XML (Version 1.9 in this screen shot).

In just a few seconds, an XML file is created. XML is a language similar to HTML that you see on many web pages, that explains exactly how the project was created, but doesn’t contain any media. It just contains all the different settings applied to each clip.

NOTE: For long-term archiving, I strongly recommend you save an XML version of every project you want to save. For example, we can convert FCP 7 XML projects easily today, but can’t convert a single FCP 7 project. XML is a long-term archiving format.

NOTE: XML files are just text files. You can open them with TextEdit and see what’s inside; for example the screen shot above is from my project. The good news is that you don’t need to understand how to read an XML file in order to use it.

At this point, the XML file is complete and ready for archiving.


Here’s a typical project in Premiere. Note that it has audio and video clips on multiple tracks, transitions, and titles. While this is a short sequence it will serve to show how the export process works.

Select the sequence you want to export.

NOTE: You can, if you want, export an XML file of the entire Premiere project. However, I tend to export the specific sequences that I need.

Choose File > Export > Final Cut XML.

First, Premiere simplifies the XML associated with this sequence, then opens a dialog where you can give the XML file a name and storage location.

NOTE: I tend to store XML files on the desktop while I am working with them, to make them easier to find, then move them into a dedicated location after the export is complete. This isn’t required, it’s just how I work.

Premiere generates, then exports an XML file to the location you specify.

Next, it creates a Translation Report of anything that won’t successfully translate.

Here’s what the Translation Report looks like for this sequence. Your Report will look different, depending on the contents of your sequence.

At this point, you can quit Premiere Pro CC. We are done with it.

The last step is to find a safe home to store your XML files. Oh! And be sure to give them a file name that allows you to find them again in the future.

Bookmark the permalink.

11 Responses to Future-Proof Media Projects: Export XML Files From Premiere or Final Cut [u]

  1. Dennis Mahaffay says:

    This is very helpful and important, Larry. Thank you!

    • Larry says:


      I agree. Look how easy it would have been to save an XML file in FCP 7 when we finished editing it; yet how difficult it is to access any FCP 7 projects today.

      Plus, XML files are tiny, so they can fit anywhere.


  2. Colin Pearce says:

    I wonder if using XML files will solve my storage problem. I record my Zoom podcast interviews and edit them in FCP X for images, deleting unnecessary dialogue etc … After exporting to iTunes and YouTube I am left with the archive library file some 50 to 120 gig large. I want to keep the originals in case I want to re-edit. Come to think of it this also applies to videos of family trips and parties. My storage is jampacked with these gigantic library files and it is cumbersome and to expensive. Any advice or pointing me to some article or tutorial I missed will be appreciated.

    • Larry says:


      NO!! ABSOLUTELY NOT! (sorry to yell)

      An XML file is a text file, not a media file. The XML simply points to where your media file is stored. Exporting XML is a good way to preserve an edit for the future, BUT it does not preserve your media. You are stuck with the large files. You can ZIP them, a little bit. But if you trash your media, nothing will bring them back.


    • Larry says:


      I gave you a bad answer earlier. Let me try again.

      If all the media stored in a library is backed up OUTSIDE the library, then, yes, you can export an XML file of your editing project, then delete the library. However, if you don’t have the media backed up, exporting an XML file will not be enough.

      To reduce the size of a Library you can do two things:

      1. Select the Library name inside the Library list in Final Cut
      2. Choose Delete Generated Library Media.

      This removes all non-essential files and should make your Libraries a lot smaller.

      If that isn’t enough, AND your media is backed up, you can delete files from the Browser using Cmd – Delete.


      • Bill Rabkin says:

        FWIW, I also am always running out of space on my external drives. Rather than using FCP’s “Delete Generated Library Media” command, I delete these generated library media using Final Cut Library Manager. This inexpensive app from Arctic Whiteness (arcticwhiteness.com) displays, for each FCP Library, a bar graph showing the size of each of the different types of generated media (Optimized, Proxy, Flow, Render). It lets me select which generated media I want to delete, and tells me how much total storage I will reclaim by doing so. It lets me move the deleted media to Trash, or delete it completely. It keeps track of whether media are available, and identifies any media files that are not found.

        I have used this app since its first release several years ago and find it extremely useful.

  3. Al B says:

    Great article. Didn’t you miss a step? The final step might be trying to reload the project again in either a different editor or the same one? I found (long ago) that I could not get a fully functional project from FCP 7 to Premiere. Many transitions and effects were no longer functioning. Just a word to the wise. Have you actually migrated some projects between NLEs? Would love an article discussing the issues you found.

  4. Robert Withers says:

    On a support call with the Adobe people, they suggested using XML to recover a Pr project fom an older version of Pr. It kind of worked, though I’ll have to do some refinishing.
    Thanks for highlighting the usefulness of XMLs.

    • Larry says:


      Happy to help. The problem with moving projects – especially XML – between software is that each NLE uses it’s own title and effects engines. XML simply says: “Apply the Gaussian Blur effect.” But FCP, Avid, and Premiere all use different technology to create the same effect.

      For this reason, effects, titles, generators that are in one system but not another, don’t transfer. Still, the bulk of our work in any project is figuring out the best way to tell the story, editing and trimming clips and applying basic transitions. That stuff all transfers.

      Cool effects and color grading, don’t.


Leave a Reply

Your email address will not be published.

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!


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