PrusaSlicer

Build  Lint  Docker Pulls  Image Size  Arch  PrusaSlicer  Unraid  License: AGPL-3.0

PrusaSlicer, in your browser. Slice from any device. No VNC client, no local install.
This runs the full PrusaSlicer desktop app inside a single container and streams it to your browser over Selkies (H.264 video), so the 3D plate stays smooth to rotate, zoom and drag, the part of slicing where the old noVNC containers feel laggy.

1. Download
2. Support
3. What it looks like
4. What it does
5. Getting started
6. How AI is used here

A one-knight job: I build it, keep it running, work through the issues and add what people ask for, until nothing is missing. It is free, with no accounts, no telemetry, no ads and no paid tier. No asterisk anywhere. Nothing readable ever leaves your own walls. Forged on evenings and weekends, with heart and stubbornness.

If it has earned a place on your server or computer, toss a coin to your knight: it helps cover the costs and keeps the project alive. It also makes this knight's heart beat a little faster. Three ways below, whichever suits you.

The models in these pictures are the 3DBenchy and the bunny from PrusaSlicer's own shape gallery, sliced in a test container.

The plater: place, scale and arrange models on the 3D build plate, right in your browser

The sliced preview: toolpaths by feature, print time and filament, then export the G-code

• The full PrusaSlicer desktop app in a single container, for amd64 and arm64. No X client, no VNC viewer and nothing to install on your workstation.
• Selkies instead of noVNC. The desktop arrives as H.264 video, so rotating, zooming and dragging on the 3D plate stays smooth, which is where the old noVNC containers lag. A GPU on the host is used when there is one, and software rendering takes over when there is not.
• PrusaSlicer from Debian trixie's prusa-slicer package, since Prusa no longer ships a Linux AppImage, so it gets Debian's security updates and runs natively on both architectures.
• Profiles that persist. Printer, filament and print profiles live in /config, and closing PrusaSlicer starts a fresh one instead of leaving a black screen.

On Unraid, install PrusaSlicer from Community Applications. Map your models and G-code folder to /storage (the template uses /mnt/user, which reaches all shares), then open the WebUI on the HTTPS port, 3001 by default.

Without Unraid:

docker run -d --name prusaslicer --shm-size=1gb \
  -p 3001:3001 \
  -e PUID=99 -e PGID=100 \
  -v /path/to/appdata/prusaslicer:/config \
  -v /path/to/models:/storage \
  junkerderprovinz/prusaslicer:latest

Open https://<server-ip>:3001/ and accept the self-signed certificate once. On the first launch the Configuration Assistant asks for your printers and filaments. After that, import a model with File → Import, slice it and export the G-code into /storage.

[!NOTE] The WebUI has no login by default, for use on a trusted network. Never expose it to the internet directly: put it behind a VPN or a reverse proxy with authentication, or set CUSTOM_USER and PASSWORD to turn on the built-in login.

Other Docker hosts

compose.yaml runs PrusaSlicer on any Linux server with Docker. Put it in a folder of its own, point the folders under volumes at your files and start it with docker compose up -d. The folders are created next to the file.

• Synology: in Container Manager, create a project from the file (DSM 7.2 or newer).
• Proxmox: run it in a VM or an LXC container that has Docker.
• MOS: install PrusaSlicer from the MOS Hub.
• ZimaOS and CasaOS: add the community store and install PrusaSlicer from it.
• umbrelOS: add the community app store and install PrusaSlicer from it.

One knight builds this, and AI is one of the tools I work with, the same way I work with an editor or a compiler. It helps me write code and documentation and it checks my work, and that saves me a good many evenings. It does not make the decisions, though. I read and understand everything before it ships, and if something here breaks, that is on me and not on the tool.

You do not have to take my word for it. The code is open and every release note is written by hand. The issue tracker shows how problems actually get handled, including the ones I got wrong the first time. If you find something that is not right, open an issue and I will look at it.

Questions, bugs, ideas or feature requests? Please open a GitHub issue.

_{The packaging in this repository is AGPL-3.0. PrusaSlicer by Prusa Research is AGPL-3.0 as well, and this project is not affiliated with or endorsed by Prusa Research. Every bundled component and its licence is listed in NOTICE.}