Canvas is not rendering

Symptoms

If one or more of these match what you are seeing, you are on the right page.

• •The canvas area is blank, black or shows the last frame frozen, while panels and menus still work
• •The Layer Panel lists your elements correctly but nothing draws
• •A prompt appears asking you to reload the page
• •The problem started after the machine woke from sleep

Causes and fixes

Ordered from most to least likely. Work down the list — each cause is paired with what to do about it.

1. 1

   The WebGL context was lost and could not be restored automatically.

   FlashFX detects context loss, re-uploads all textures from CPU memory and resumes without a reload. When restoration fails it prompts you to reload — do so. Work in a cloud-synced session is preserved across the reload.

2. 2

   Hardware acceleration is disabled in the browser.

   FlashFX requires a WebGL-capable context. Re-enable hardware acceleration in your browser settings and restart the browser, then reload the editor.

3. 3

   An enterprise security policy is blocking WebGL.

   This is most common on managed Edge and Chrome installations. If FlashFX cannot initialise the GPU context on a work machine and works on a personal one, the policy is the difference — check with your IT administrator.

4. 4

   A single texture exceeds what the GPU driver will accept.

   In Chrome, textures larger than 8192×8192 can fail silently on some drivers. Keep imported assets at or below the 8K maximum rather than relying on larger source files.

5. 5

   A browser extension is interfering with the canvas.

   Reload the editor in a private window, which runs without extensions. If the canvas renders there, re-enable your extensions one at a time to find the one responsible.

Related pages