← All how-tos

Setup OrcaSlicer with your 3D printer over Wi-Fi

OrcaSlicer 2.4.2 · Windows 10 / 11

OrcaSlicer turns a 3D model into the G-code your printer runs. Installing it is a download and a short wizard. The part that trips people up is the last mile — telling the slicer where the printer lives on your network, so you can send a print without carrying a microSD card across the room.

There is also a field in that dialog that almost every guide skips. Miss it and everything appears to work — you can slice, you can print — but the Device tab shows a blank 404 Not Found forever.

The short version. Connect the printer with Browse… in the Physical Printer dialog, then — before clicking OK — fill the Device UI field with your printer’s own web interface: http://<printer-ip>:4408/ on a Creality K-series. That single field is what the Device tab loads, and leaving it blank is why the tab returns 404 even though printing works. The long version, with every screen, is below.

Two parts: install, then connect. If OrcaSlicer is already set up, skip to part two.

Every screenshot below is a real frame from one session, recorded while someone actually did this with Navisual — an assistant that watches the screen and marks the control you need next. The orange marks are Navisual pointing; the strip along the bottom is the instruction it spoke.

Before you start

• Windows 10 or 11, about 400 MB free.
• The printer must be on the same network as the PC. Not just “on Wi-Fi”. If the scan in step 5 comes back empty, the usual cause is the printer on a 2.4 GHz guest SSID and the PC on the 5 GHz main one. Same router, different networks, no discovery.
• This page was checked on a Creality K2 Plus. Port 4408 is the Creality K-series web interface. On other hardware the field is still the answer; the port may not be. See the troubleshooting section.

Part one: install

1. Download the Windows installer. OrcaSlicer lives on GitHub, not in an app store. Open the releases page and take the newest entry marked Official Release — skip anything labelled Nightly, Beta or Alpha.

   Release notes come first; the downloads are at the bottom under Assets. There are a dozen files and most are not for you — Linux flatpaks, an AppImage, a macOS .dmg, portable zips, a debug build. You want OrcaSlicer_Windows_Installer_..._x64.exe, about 131 MB. Note x64, not arm64, unless you are on an ARM machine.

   

2. Pick your printer in the setup wizard. Run the installer, click through the licence and install location, then work through the first-run wizard. Only one page changes an outcome: Printer Selection.

   The list is long, grouped by vendor, and opens on whoever is first alphabetically — nowhere near you. Use the search icon in the top left rather than scrolling, tick the box on your printer’s card, and click Next.

   This is what fills in your bed size, nozzle diameter and print profiles. Get it wrong here and every print afterwards is wrong.

   

3. Click Next through the rest. Nothing else needs a decision on a first install. Tick the filament types you actually own — PLA is enough to start, and you can add more later from the Filament dropdown. Leave Stealth Mode off; it only stops OrcaSlicer’s own network calls and does not affect talking to your printer. Leave Install Bambu Network plug-in unticked unless you have a Bambu Lab machine.

   Click Finish, then New Project to land in the workspace, with your printer, nozzle and filament down the left and a build plate sized to your machine.

The question changed here

Worth noting, because it is what the rest of this page came out of. At this point the session stopped being about installing anything. Instead of moving to the next step, the user typed a new question into the panel:

how to connect to my 3D printer using wifi? It is a Creality K2+ and it is turned on.

Navisual kept the screen it was already looking at, rewrote its plan from Install and setup Orca Slicer to Connect Creality K2+ 3D printer to OrcaSlicer over Wi-Fi, and carried on from the same window. Everything below came out of that one sentence.

Part two: connect over Wi-Fi

4. Open the connection settings from the Wi-Fi icon. In the left rail, the Printer header has a small Wi-Fi icon beside it. That is the entry point, and the first place people get stuck: it is not on the Device tab, which is what the name suggests, and it is not in the File menu. It is a glyph a few pixels wide next to a heading.

   

5. Scan the network and select your printer. The Physical Printer dialog opens. For a Creality K-series, set both Host Type and Printer Agent to CrealityPrint.

   You can type the IP by hand if you know it, but Browse… next to Hostname, IP or URL scans the local network and finds it — no trip to the printer’s touchscreen. Click the row for your printer, then the green Use Selected button below the list.

   Write the IP down. Step 6 needs it, and this dialog is the easiest place to read it.

   

6. Fill in Device UI — the step that prevents the 404. Back in the Physical Printer dialog, Hostname, IP or URL is now filled in and it is tempting to press OK. Do one more thing first.

   The Device UI field is what the Device tab loads. Leave it empty and that tab shows a bare 404 forever. Fill it with your printer’s own web interface — the same IP, on port 4408:

   http://192.168.0.88:4408/
   

   Substitute your own address. API Key / Password and HTTPS CA File stay empty on a standard Creality setup. Save Machine as at the top names this connection in your printer list — worth editing if you run more than one machine. Then click OK.

   

7. Check the Device tab. Open Device along the top. OrcaSlicer loads the printer’s own interface inside the tab — on a Creality K-series that is fluidd: live bed, nozzle and chamber temperatures, recent jobs with their durations, axis jog controls and a console, without leaving the slicer.

   Slicing a model now gives you a Print button that sends the job over the network instead of writing G-code to a card.

   

If the Device tab still shows 404

In order:

• Check the port. 4408 is the Creality K-series web interface. Other hardware differs — a Klipper machine running Mainsail or fluidd directly is usually 80 or 81, and some builds use 7125 for the Moonraker API rather than the UI. The quickest test is to open the same URL in a browser on the same PC: if the browser shows the interface, that exact URL belongs in Device UI; if the browser 404s too, the port is wrong and OrcaSlicer is only relaying the printer’s answer.
• Include the scheme. http:// at the front. A bare 192.168.0.88:4408 is not a URL and the embedded browser will not guess.
• Do not put the Device UI address in the Hostname field. Different fields, different jobs: Hostname, IP or URL is where prints are sent, Device UI is what the tab displays.
• Confirm it saved. Closing the dialog with the red X rather than OK discards the edit, and the tab keeps showing 404 with no sign the field was ever touched.

Why this is hard to find

1. The connection works without it. Fill in the IP and you can slice and send a print. Nothing warns you a second field exists, so guides that end at “Use Selected, OK, done” are not wrong — they are answering a different question.
2. The failure is silent and in the wrong place. The field you skipped is in the Physical Printer dialog; the symptom appears on a Device tab that looks like a separate feature. Nothing on screen links the two.
3. The port is hardware-specific and undocumented in the app. OrcaSlicer asks for a URL and offers no hint what yours is. 4408 comes from Creality’s firmware, not from anything in the dialog.

The field also reads as optional. It sits between Hostname, IP or URL and API Key / Password, both of which genuinely are optional on a local network, and it has no asterisk, no placeholder and no tooltip.

How this guide was made

Nothing here was written from memory or rebuilt from a manual. Somebody sat down at a Windows machine and asked one question — “how to install and setup Orca slicer for my 3D printer?” — and Navisual guided them through it one control at a time, drawing a mark on screen and speaking each instruction. The screenshots above are the frames it captured.

• The session ran 20 steps across 18 exchanges, in one sitting, from an empty browser tab to a live printer dashboard.
• 16 of 20 controls were pinpointed on screen. Two steps were scrolling or summaries with nothing to point at; one fell back to the model’s own visual estimate, which was correct.
• It changed course twice — once when the question changed mid-task, once when a step led to a 404 and had to be worked back from. Both are in this guide rather than tidied out of it.
• Edited: screenshots are cropped to the application window except the two that show the Navisual panel; the desktop behind it is the author’s and is nobody else’s business. Repeated clicks were merged and the no-decision wizard pages compressed into one step.
• Not edited: every orange mark is where Navisual actually drew it, including the one on a button it could not name.

---

Checked on OrcaSlicer 2.4.2 with a Creality K2 Plus on Windows 11 in September 2026. Every screenshot is a real frame from one session, and the orange marks are Navisual pointing at the control named in the step beside them.

---

Steps like these are easier when something points at the actual control on your screen. Navisual reads what is in front of you and shows you where to click. It never clicks for you.