Edge
Safari
Firefox
DuckDuckGoMost failed exports are range or encoder problems rather than corrupt projects. The export range defaults to the work area, so an In/Out pair set during preview will silently constrain what is rendered — and advanced video export depends on browser APIs that older versions do not implement.
If one or more of these match what you are seeing, you are on the right page.
Ordered from most to least likely. Work down the list — each cause is paired with what to do about it.
Export uses the work area In and Out points as its default range. Press Ctrl+Alt+F in the timeline to fit the view to the full project duration and confirm the range, or set the range explicitly with the export range override in the export dialog.
The VideoEncoder API is available in Safari from 16.4; earlier versions fall back to a slower export path that can appear stalled on long compositions. Export from Chrome or Edge for the fastest and most reliable encode.
Export renders at full resolution regardless of preview quality, and at 4K the cost of filters multiplies. Reduce the number of simultaneous offscreen-buffer effects, or export at a smaller canvas size to confirm the composition is the cause.
Transparent backgrounds export only to formats that support alpha — PNG, WebM with alpha, and single-frame PNG. Exporting a transparent canvas to MP4 produces an opaque result.
This combination can produce composite errors at element boundaries. Set 3D elements to Normal blending for transparent exports, or export over a solid background and key it later.
If none of the causes above match, contact support with the steps to reproduce the problem, your browser and version, and any message from the browser console. You can reach us at support@flashfx.app.
Contact Support