Start by reading a copy as text
If a double-click opens the wrong application, use Open With and choose a plain-text or code editor. On Windows, Notepad can show the contents; on Mac, use a text editor without converting the file to rich text. A code editor can add indentation and syntax highlighting. Keep the original unchanged while investigating an unfamiliar file.
Reading the text is different from importing the data. A text editor can show tags from many XML formats; a spreadsheet or video editor accepts only the structures it knows how to interpret. If you only need to understand what you received, there is no need to convert it first.
Look for the root element
Skip the optional XML declaration and any comments. The outermost element is a useful first clue. For namespaced documents, the namespace URI also matters: the root name alone is not proof of compatibility.
| Clue | Likely purpose | Next step |
|---|---|---|
| xmeml | FCP7 editing interchange | Check sequence, source references and frame rate. |
| fcpxml | Final Cut Pro XML interchange | Check the version and supported timeline structures. |
| urlset / sitemapindex | Website sitemap | Use website or search-indexing tools. |
| rss | RSS feed | Use a feed reader or inspect the entries. |
| Other names | Application-specific data | Ask which program created it and what output is needed. |
Why an XML file may fail to open
A syntax error can come from an unclosed tag, incorrectly nested elements, unescaped characters or a file truncated during transfer. Check the line identified by the application and the element immediately before it. If the file came from an export, request a fresh export before attempting extensive manual repairs.
A different message, such as unsupported document or unknown format, can mean the XML is readable but belongs to another application. Renaming it to .fcpxml or .edl does not change its internal structure. A missing-media message usually concerns the files referenced by an editing XML, rather than XML syntax.
Choose the output by the contents
For business records, XML-to-CSV requires choosing which repeated element becomes a row and how nested values become columns. XML-to-JSON requires decisions about attributes and repeated elements. XML-to-PDF requires a layout or a rendering application. A generic conversion should be checked against the original records; a file extension cannot supply that mapping.
For video timelines, use the originating editor or a converter that supports the specific dialect. EDL Toolbox can inspect supported FCP7 XML and basic FCPXML and convert them to EDL or offline AAF. This is separate from general-purpose data conversion.
When the XML opens but the edit is offline
Ask for the referenced media, the intended sequence start, playback rate and a reference movie. An XML copied to another computer can still point to paths that exist only on the original machine. Relinking restores those associations in the receiving editor; converting the XML cannot recreate missing footage.
For a useful support request, include the originating application and version, the root element, intended output and exact error. Use a small synthetic example if the original contains confidential project names or paths.