Edge
Safari
Firefox
DuckDuckGoEditor slowness is almost always rendering cost rather than a fault. FlashFX composites the canvas on the GPU, and blur, non-Normal blend modes, alpha masks and isolated groups each force an additional offscreen framebuffer. Enough of them on a limited-VRAM device will slow the whole application.
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.
Switch preview quality to Half or Quarter in the transport bar dropdown. This affects only the live canvas preview — export always renders at the full project resolution.
Non-Normal blend modes, blur effects, alpha masks, some distortion effects and isolated groups each need an intermediate framebuffer sized to the canvas. Right-click an element in the Layer Panel and choose Profile Element to see how many buffers it requires, then simplify the worst offenders.
Every image occupies GPU texture memory at its source resolution regardless of display size — a 4096×4096 image costs roughly 64 MB whether it fills the canvas or a thumbnail. Resize images to their rendered dimensions before importing.
Run Animation → Pre-render Preview to cache the frames in the work area before playing. Cached frames — shown by the green bar in the timeline ruler — play back at the full project frame rate regardless of composition complexity.
Undo History Depth defaults to unlimited. On long sessions with complex projects, set a numeric cap in Edit → Preferences (Ctrl+,) to reduce memory pressure.
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