Articles on: Cloud Slicer

Slicer is slow or is lagging

Slicer is slow or is lagging


Cloud Slicer performance depends on what is slow. Importing, moving models, painting, and previewing happen in your browser. The actual slice job runs on SimplyPrint's slicing service.


If the 3D view is slow

The 3D view uses your browser and graphics hardware. Large models, many objects, dense meshes, and G-code previews can make the page feel slow.


Try this:


  1. Close other heavy browser tabs.
  2. Refresh the slicer.
  3. Use a current version of Chrome, Edge, Firefox, or Safari.
  4. Make sure hardware acceleration is enabled in your browser.
  5. Reduce the number of objects or plates in the project.
  6. Avoid previewing very large sliced files on low-memory devices.


If slicing is waiting

If the page is responsive but the slice itself is waiting or queued, that is not caused by your browser. The task is waiting for the Cloud Slicer service to process it.


For quota and queue details, see Cloud Slicer quotas, limits, and usage.


If G-code preview is slow or crashes

G-code preview can be heavy because the browser has to draw the sliced toolpath. Very large prints, many tiny moves, or high layer counts can use a lot of memory.


If preview causes problems, disable preview for that device or download the sliced file instead.


For more detail, see G-code preview causing browser crashes or freezing.


If painting is slow

Paint-on tools can slow down on very dense meshes. Try using a smaller model, reducing mesh detail before upload, or using the fill brush for larger connected surfaces instead of many small strokes.



Updated on: 26/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!