Known Constraints by Browser

• -Best WebGL 2.0 support
• -Hardware acceleration defaults on
• -Best export performance (uses Chrome's built-in video encoding APIs)
• -Known issue: Very large single textures (greater than 8192x8192) may cause silent failures on some GPU drivers. Use the 8K maximum instead of larger.

• -Full WebGL 2.0 support
• -Slightly different default memory limits for offscreen buffers
• -The webgl.max-warnings-per-context setting must remain at default to avoid performance warnings during heavy rendering
• -Known difference: Antialiasing on canvas edges may differ slightly from Chrome; visually negligible for export

• -WebGL 2.0 support from Safari 15 and later
• -Metal GPU backend (not OpenGL) — generally excellent GPU performance on Apple hardware
• -Canvas drawImage performance (used in certain compositing paths) is slower than Chrome in some versions
• -Advanced video export (VideoEncoder API) available from Safari 16.4 and later; older versions fall back to a slower export method
• -Known limitation: EXT_disjoint_timer_query (used by the performance profiler) is disabled in Safari for security reasons — GPU timing data may be unavailable

• -Chromium-based — essentially identical behavior to Chrome
• -Some enterprise security policies may restrict WebGL; check with IT if FlashFX fails to initialize the GPU context

In all browsers, the WebGL context can be lost due to GPU driver crashes, system sleep, or GPU reset. FlashFX handles this by:

1. 1.Detecting the context loss event
2. 2.Automatically attempting to restore the context
3. 3.Re-uploading all textures from CPU memory
4. 4.Resuming rendering without requiring a page reload

If context restoration fails, FlashFX prompts to reload the page. Current unsaved work in the cloud-synced session is preserved.