G-code preview causing browser crashes or freezing

G-code preview is rendered in your browser. For very large sliced files, high layer counts, or dense toolpaths, preview can use enough memory to slow down or crash the tab.

The sliced file may still be valid even if the browser cannot comfortably preview it.

What the crash warning means

If Cloud Slicer detects that preview may have caused a crash, it can ask whether you want to keep preview enabled or disable it on this device.

Disabling preview affects the current browser or device. It does not delete the sliced file and does not change the print settings.

What to do

If preview freezes or crashes:

1. Reload the page.
2. Disable G-code preview for this device if the warning appears.
3. Download, save, queue, or print the sliced file without opening preview.
4. Try a smaller model or lower-detail model if preview is important for the job.

When to keep preview enabled

Keep preview enabled if the issue happened once and you still want to inspect sliced files in the browser.

You can also preview a single file when needed instead of always opening preview automatically.

When to disable preview

Disable preview if the same device repeatedly crashes or freezes after slicing. This is especially useful on older laptops, tablets, or browsers with limited memory.

Related articles

• How G-code preview works after slicing
• How to slice, preview, download, and send sliced files
• Slicer is slow or is lagging
• How to download, queue, direct print, or multi-print sliced output

Updated on: 26/05/2026