Export Reference
Browser and Mac export details, quality tiers, the export page, Share panes, editable timeline handoffs, and Klipeo server render limits.
The reference behind Exporting Video.
Device export
This encodes the video right in your browser, with no queue and no waiting.
- On browsers with WebCodecs (most modern ones) you get a real MP4, H.264
video with AAC audio mixed from your timeline, downloaded as
<project>.mp4. - On browsers without WebCodecs, it falls back to a realtime WebM recording
(VP8 or VP9, depending on the format you picked). The fallback keeps your audio:
the recorder plays the mixed timeline audio buffer into a
MediaStreamDestinationand records that track alongside the canvas. - Quality: Low (2.5 Mbps), Medium (5), High (10), or Very High (20).
- It renders at your composition's resolution and frame rate and shows a live percentage. You can hit Cancel mid-encode; the card then reads Export cancelled with Try again and Back to editor.
- The render lives in this tab, so leaving mid-encode would lose it. Back to editor, the browser's back button, and any Connect button ask Stop exporting? first, with Keep exporting and Stop and leave; closing or reloading the tab gets the browser's own prompt. The same question appears while a finished file is uploading to Klipeo for sharing.
The export page fits one screen: the file name, settings pills, and a status card with live progress on the left, the video on a 16:9 stage on the right (a vertical video sits letterboxed inside it), and the send tiles under the stage. Duration is the exported length after Cut and Speed regions, not the full composition ruler.
Include audio lives in the export dialog.
Nothing on the timeline
If the timeline is empty, the export fails with "Nothing to export, timeline is empty." Add at least one clip first.
Share instead of exporting
The header's Share button holds five panes. Video picks the format (MP4, MP4 · H.265, or WebM in the browser), resolution, and frame rate (24, 30, or 60 fps) and starts the export; More options: quality, presets, subtitles opens the full export dialog with quality, presets, timeline handoff, and subtitles. People invites collaborators to edit, comment on, or view the video; see Collaborators & Presence. Link and Embed share a render without a download; see Sharing and Embedding. Script exports the written guide once the Script tab has one.
Continue editing in another app
Use Editable timeline handoff in the export dialog when you want to finish the cut in a desktop editor. Each download preserves the portable parts of the edit, including clip timing, source in and out points, tracks, media references, captions, and markers. Expand Export report after the download to see every item that needs relinking or recreation.
| Destination | Download | Caption workflow |
|---|---|---|
| Final Cut Pro | FCPXML 1.9 (.fcpxml) | Captions are included in the timeline. Import it with File → Import → XML. See Apple's FCPXML import guide. |
| DaVinci Resolve | Resolve-safe FCPXML 1.9 (.resolve.fcpxml) | Caption timing and text are included as duration markers. Download the SRT too, then import it as the subtitle track. |
| Adobe Premiere Pro | Final Cut Pro 7 XML / XMEML v5 (.xml) | Captions and Klipeo text are included as title clips. Import the XML with File → Import. Adobe documents the supported workflow in Importing XML project files. |
| CapCut | Rendered MP4 plus SRT | CapCut does not import third-party project XML. Import the rendered video, then follow CapCut's subtitle import steps on Desktop or Web. |
No single XML dialect works identically in every editor. The Final Cut download keeps FCPXML captions, while the Resolve download replaces those nodes with markers because Resolve rejects them. Premiere receives the cut and source ranges, but its XML interchange cannot reproduce every Klipeo transform, crop, speed change, mask, transition, or effect. The export report identifies the affected clips.
Keep the source media
XML contains edit decisions and media references, not the media itself. If Klipeo only has a browser or remote URL for an asset, the destination editor imports that clip offline. Use its relink command to point the clip to the original file named in the export report.
Klipeo server renders
The editor does not offer server rendering right now: the Where it renders choice shows only Your browser, and every export encodes on your device. The renderer itself stays in the product, so render jobs created earlier still show on the Renders page. The limits below apply when it is offered again.
What the server render cannot do
The server render is not a superset of the browser export. Before a job renders, the worker checks the composition against what Remotion can reproduce, and a job that uses any of the following fails outright:
- A visible Cut or Speed region on the timeline.
- Chroma key on a visible clip, and other visual effects the SVG grade cannot reproduce. A clip's Color correction renders on the server unless it uses a LUT, an HSL qualifier, Mid/Detail, hue curves, a vignette, or Magic Mask.
- Effect layers other than camera layouts and Record panel masks, and HSL, LUT, or Mid/Detail features on an Adjustment layer.
- Audio effects on an audible clip that is sped up or slowed, an audio effect type this server does not know, and variable-speed audio from time remapping. Other clip audio effects render on the server with the same code as the browser.
- A text font that is not one of the editor's own fonts.
- Media the renderer cannot fetch.
A failed server job says what happened in plain words and offers Try again and Render in browser instead. It also appears on the Renders page with the reason on hover.
Platform presets
When server rendering is available, a Platform presets card lets you queue several deliverables at once. Tick the ones you want and press Queue N renders:
| Preset | What you get |
|---|---|
| YouTube 1080p | 1920×1080, H.264, 8 Mbps |
| YouTube 4K | 3840×2160, H.264, 40 Mbps |
| Instagram Reel | 1080×1920 vertical, 6 Mbps |
| TikTok | 1080×1920 vertical, 5 Mbps |
| Twitter / X | 1280×720, 5 Mbps |
Only MP4/H.264 presets can be rendered on our servers today, so the ProRes HQ, WebM VP9, and GIF presets in the codebase don't appear in this list yet.
The queue runs two at a time and each row shows its own status with a Download link when it lands. Keep the page open until the queued renders dispatch. Every job also shows up on your Renders page.
Server render limits
What the server will accept
- Two renders at a time per account. A third request comes back as busy and the batch queue simply waits its turn. - A daily render quota per account, separate from your AI usage. When you hit it you get "Daily server-render limit reached" with the UTC reset time. - Spec ceilings: 3840×2160, 60 fps, 60,000 kbps video, 512 kbps audio. - Cancel render stops a job in flight. - The page stops polling after 10 minutes with "Render timed out, check the Renders page for status". The job itself may still finish, so check Renders.
Server renders show up on your Renders page where you can track and re-download them. To send a finished video to YouTube or TikTok, see