Star 168 Get Started
← Blog

Connecting a Prusa printer to PrintStash through PrusaLink

Set up the beta PrusaLink provider for local status, upload and start, remote file inventory, and job control, without Prusa Connect cloud.

guideprusaprusalink

PrusaLink is the web interface running on the printer itself, and PrintStash talks to it directly over your LAN. Nothing routes through Prusa Connect, so the setup works on a network with no internet access at all.

The provider is beta. It covers the operations most people want, and a few things Moonraker offers are missing.

Find the credentials on the printer

On an MK4 or XL, go to Settings -> Network -> PrusaLink on the printer’s own screen. That page shows the username, which is maker by default, and the password. The IP address is one level up under Settings -> Network -> IPv4 Address.

Confirm those credentials work before involving PrintStash. Put the IP into a browser, log into PrusaLink, and check that you can see the printer. If that fails, fix it there first, because PrintStash cannot succeed where the printer’s own interface does not.

PrusaLink accepts modern Digest username and password credentials or a legacy API key, and PrintStash supports both. Prefer Digest where the firmware offers it.

Add it to PrintStash

Open Printers -> Add printer, choose PrusaLink, and give it a name plus the LAN address you just used in the browser. Enter the Digest username and password, or the API key on older firmware.

Use a name that stays clear in alerts and print history months from now. MK4-textured-PETG beats Prusa 2 when a notification arrives at midnight.

After saving, open the Diagnostics tab. It reports the provider’s support level, capability checks, unsupported actions, configuration problems, and live connectivity, and it never returns stored secrets, so the output is safe to paste into a help request.

What you get

A connected PrusaLink printer gives live status, upload from the vault with optional start, remote file inventory including deletion, and pause, resume, and cancel on the running job.

The v1 API handling was corrected in v0.11.0: file listings recurse into folders properly, job telemetry reads from the right fields, and starting a file uses POST /api/v1/files/local/{path}. If you tried this provider on an earlier release and the file list looked wrong, that is why.

What is missing

No raw G-code and no emergency stop. Those stay in PrusaLink or on the printer.

No measured filament consumption. Moonraker reports actual grams and duration back from the job and PrusaLink does not, so cost history for these machines rests on the slicer’s estimate. Spoolman consumption write-back is Moonraker-only for the same reason. A farm mixing Prusa and Klipper machines will simply have better numbers on the Klipper side.

Print history import is also Moonraker-scoped, so past jobs do not backfill onto your models from a Prusa machine.

Smoke test before you trust it

  1. Confirm the status on the printer page changes when the printer’s state changes.
  2. Sync the remote file list and check it matches what PrusaLink shows.
  3. Upload a small known-good G-code file with start disabled.
  4. Confirm the file appears in PrusaLink’s own interface.
  5. Only then test start, pause, resume, and cancel, and only on a machine where a mistake costs nothing.

Beta means shipped and usable while hardware coverage is still growing. Treat the first print through a new provider as the test it is.

The compatibility matrix lists exactly what this provider can do next to the others, and connecting Klipper through Moonraker covers the stable provider if your fleet is mixed.

Sources