Export & Deploy

Export MP4E videos and deploy them anywhere using the MP4E Player SDK.

Overview

Studio can export:

  • MP4E video: an MP4 with MP4E metadata embedded
  • Metadata JSON: the portable schema (great for review and automation)

Export Video (MP4E)

Use Export (or File → Export Video) to download the MP4E file.

Search card. When the video has been analysed, the exported file also carries a public search card — title, summaries, topics, the things in the video (each with its category), chapters, key moments, search phrases, the questions the video answers and the public part of its catalogue (tags, licence and rights, the custom fields marked public, and the date it was recorded) — so search engines, media libraries and AI assistants can find it. Two switches under Library panel → Settings → Search card control it: Include a search card in exported videos (on by default) and Include the full transcript (off by default). The Export dialog repeats them as Include search card and Include transcript toggles, starting from those settings, so you can leave the card (or just the transcript) out of one export without changing the project; the card toggle is disabled until the video has been analysed, and the transcript toggle is disabled while the card is off. See Searching MP4E Videos.

Private details. An exported file leaves out what the project keeps private: the catalogue's owner, client, project and private custom fields; where, at what time of day and on which device the video was filmed (only the date stays); analysis items you hid or kept private (the item itself goes; mentions of it in the video summary and in other scenes' descriptions stay, and a hidden or private chapter leaves a gap in the exported chapters), and the history of your edits (who changed what). The text of the scenes' dialogue and the analysis diagnostics are emptied too. Your corrections themselves are kept — the file carries the analysis as you edited it. The camera's own tags in the file go too: its GPS position, make, model and software, GPS telemetry tracks (GoPro, iPhone, 360° cameras) and XMP. Images and videos you added to the media library are carried as you uploaded them, with any location data of their own. The Export dialog's Include private details toggle keeps all of it for one export — for your own archive copy. It starts off every time; the project and its stored video are never changed. If the video file's own metadata cannot be cleaned with certainty (for example a fragmented file with a telemetry track), the export is refused with a message to export again with Include private details.

Stream interactive data (faster start on long videos). Off by default. On, the exported file keeps its object tracking apart from the rest of the interactivity: the metadata is a small signed start document, and the tracking is stored beside it as encrypted chunks, so a player does not have to read the whole timeline before it starts — which pays off on long or tracking-heavy videos; on a short video a whole-document export can start just as fast. The start document can carry the tracking for the first frames; the player then fetches the chunk at the playhead first (again after every seek) and the chunks just ahead of playback, so objects appear as soon as their frames are loaded. The chunks are fetched with HTTP range requests; with the player's enableBlobCache on, once the whole file is downloaded every chunk is read from it instead, so a server that ignores range requests still gets its object tracking after the download. The player reports progress with the timeline:* events. Like the other toggles it applies to one export and never changes the project; the project's settings.streamTimeline and the API's streamTimeline parameter set the same switch. A streamed export is for playback: uploading it to create a new project is refused — upload the original video, or an export made with this toggle off.

If Export is blocked
Export requires that the video has metadata (run processing first).

Export Metadata JSON

Use File → Export Metadata JSON to download the complete current metadata state (including your local edits like layers, variables, sceneGroups, and settings).

Import Metadata JSON

Use File → Import Metadata JSON to replace the project metadata with a JSON file. Studio then reloads the project and applies the imported state.

JSON import is great for automation
Many teams generate overlays/rules programmatically (or via AI) and import them into Studio for final polish and preview.

Deploy with the Player SDK

Once you have an MP4E video file hosted somewhere accessible, embed it using @mp4e/react.

React embed (Player SDK)
1import { MP4EPlayer } from '@mp4e/react'
2import '@mp4e/react/styles.css'
3
4export function MyExperience() {
5 return <MP4EPlayer src="/videos/my-video.mp4" />
6}
Next steps