OrcaSlicer for the Creality K2

Community test build of OrcaSlicer with native Creality K-series support — LAN auto-discovery for K2 / K2 Plus / K2 Pro, live CFS filament-slot sync from the printer, and the 191 K2-specific filament profiles from Creality Print imported in. Built on top of imammedo's upstream PR #13291. We're working with the OrcaSlicer maintainers to land this upstream; help from K2 owners testing in the real world makes that case far stronger.

Build 2026-05-20 Commit c27339d Windows 10 / 11 · Linux Portable — no installer
Windows zip Linux AppImage Windows: extract, run orca-slicer.exe. Linux: chmod +x the AppImage, then run.

What's in this build

Four K-series additions on top of upstream OrcaSlicer

All four changes live on the public harktech/k2-discovery branch and are open as Draft PRs against the upstream repo — this build is just an easy way to try them without compiling.

  • LAN auto-discovery (K2 / K2 Plus / K2 Pro)
  • CFS filament-slot sync
  • 191 K2 filament profiles imported
  • Mainsail web UI as the Device tab
  • Open source · AGPL-3.0

What changed

LAN discovery + CFS sync

K-series printers announce themselves via DNS-SD under a per-device-unique service name (_Creality-<mac>._udp) which OrcaSlicer's existing Bonjour browser can't find. This build adds a Creality-specific scanner: click Browse... in the Physical Printer dialog and your K2 appears in 5–10 seconds — no typing IPs.

The AMS-sync icon now queries the K2's CFS over WebSocket, reads the slot data (vendor, type, brand name, colour, pressure-advance) and updates Orca's sidebar with the brand-specific filament preset that actually matches the loaded spool. No more “Generic PLA” placeholder when you've got Hyper PLA loaded.

Profiles + device tab

191 K2-family filament profiles (PLA / PLA-CF / PLA-GF / ABS / ASA / PA / PC / PET / TPU, K2 + K2 Plus + K2 Pro) imported from Creality Print v7.1.1. Brand-specific presets — eSun PLA+, Hyper PLA, Polymaker PolyTerra, etc — show up in the filament dropdown straight away.

The Device tab shows Mainsail at http://<ip>:4408 instead of the empty Bambu-only panel, so you get the full Klipper web UI (camera, console, macros, gcode files) inside the slicer.

Get started

Quick start

  1. Download & extract the zip anywhere — e.g. C:\OrcaSlicer-K2\. It's a portable build, no installer, no admin rights, doesn't touch your existing OrcaSlicer install. To revert, just delete the folder.
  2. Run orca-slicer.exe. First-launch wizard: pick your machine. There's a Creality K2 / K2 Plus / K2 Pro entry; choose the one you have.
  3. Add the printer connection: in the device list, click the ☰ menu › Add Physical Printer. Set Host Type = Creality Print. Click Browse… next to Print Host URL — a busy cursor appears for 5–10 seconds while the LAN scan runs, then the discovery dialog opens with your K2 listed. Select it › Use Selected.
  4. Sync CFS filaments: in the sidebar, click the AMS-sync icon next to the filament rows. Your CFS slots populate with the brand-specific filaments currently loaded. Slice as usual.

First launch — what to expect

The build is not code-signed, so on first launch Windows SmartScreen will say “Windows protected your PC”. This is a generic warning shown for every unsigned executable from a small publisher — it doesn't mean anything is wrong with the file. To launch: click More info › Run anyway.

If you'd like to verify the zip matches what we published before extracting it, see “Verify your download” below.

Before you run it

Requirements

  • Windows 10 or 11 (any edition). Linux / macOS builds are not yet packaged — build from source for now.
  • Creality K2, K2 Plus or K2 Pro on the same LAN as your PC. Wired ethernet on the PC is helpful (more reliable mDNS than Wi-Fi).
  • K2 firmware that exposes the Creality WebSocket on port 9999 (any recent stock firmware does).
  • ~370 MB free disk space once extracted.

Known limitations

  • End-to-end tested on a K2 Combo (F021, firmware v1.1.260206). K2 Plus / K2 Pro should work but are untested in the wild — your feedback is what tells us they do.
  • Wi-Fi client isolation on some routers (especially mesh systems) will block the mDNS discovery. If the dialog finds nothing, that's the first thing to check.
  • This is a test build. Some upstream features may have minor regressions inherited from the base PR (#13291) it stacks on.

Verify your download

SHA256

Run this in PowerShell after downloading, and check the output matches:

Get-FileHash OrcaSlicer-K2-Test-2026-05-20-c27339d.zip -Algorithm SHA256

08203A21FE13B203D8FD1E7F0C4620BA97BA3559B4EC81FC6EC49848C327D206

Companion file: OrcaSlicer-K2-Test-2026-05-20-c27339d.zip.sha256

Help us land it upstream

How to give feedback

The whole point of this build is to gather real-world test signal for the upstream OrcaSlicer maintainers. If you try it, please drop a comment on whichever PR is relevant — one-liners (“works on my K2 Plus”, “CFS sync didn't pick up my third slot”) are exactly what we need:

CFS filament sync

PR #13744 — the AMS-sync icon pulling slot data from your CFS over WebSocket.

LAN discovery

PR #13752 — the Browse… button finding K-series printers via DNS-SD.

CrealityPrint host (the base)

PR #13291 by @imammedo — everything else stacks on this. Worth a thank-you comment.

Source & attribution

Open source, with credit where it's due

  • This build's source: grant0013/OrcaSlicer @ harktech/k2-discovery — two commits on top of harktech/cfs-agent-protocol (PR #13744). Required by AGPL.
  • Upstream OrcaSlicer: SoftFever/OrcaSlicer, licensed AGPL-3.0. Everything here is a follow-up to @imammedo's PR #13291 which adds the Creality Print host type.
  • mDNS library: mjansson/mdns (public domain). C++ wrapper cxmdns from CrealityPrint v7.1.1 (AGPL-3.0). Attribution in src/slic3r/Utils/mdns/NOTICE.md.
  • Filament profiles: imported from CrealityPrint v7.1.1 (AGPL-3.0). Attribution in resources/profiles/Creality/NOTICE.md.
  • Built & packaged by Hark Tech on a self-hosted GitHub Actions runner (VS 2026 / MSVC 14.51).

Builds

Pick a build

Each release is a portable Windows zip pinned to a git commit so you can rebuild from source. Older builds kept for reproducibility — the latest is always recommended.

2026-05-21 Latest commit 3add4012 · Windows 10/11 zip (~154 MB) · Linux AppImage (~135 MB)

Hot-fix on top of the earlier 2026-05-21 build. The 10 CR-PETG filament profiles added that day inherited from a base template (fdm_filament_petg) that didn't exist in the bundle — OrcaSlicer aborted the Creality filament load on parse error, leaving the K2 absent from the printer dropdown after testers added it. Fix repoints all 10 CR-PETG profiles at the existing fdm_filament_pet base, which already declares filament_type: ["PETG"]. No other changes vs b513dff2. If you tried the earlier 2026-05-21 build and the K2 wouldn't show in the dropdown, this is the fix. Everything else carries forward: K2 Plus CFS state-fix, LAN auto-discovery (PR #13752), CFS filament-slot sync (PR #13744), Creality HF Generic vendor categorization, Mainsail web UI, and the rest. Stacks on imammedo's PR #13291.

Windows zip Linux AppImage
SHA256 (Windows) 
FF806F20CB195DA8E1095DF823F7D80A7B28494F9DA410D757C848896353D47D
SHA256 (Linux) 
43d5c03d2f1c02390a7cb7b6766cc90f626cc639cd7c52d5a52ccadf34b2f2d3

Ready to try it on your K2?

Portable Windows zip (~154 MB) or Linux AppImage (~134 MB). No installer, no account. Comments on the PRs go directly to the OrcaSlicer maintainers.

Download OrcaSlicer K2 (test build)

Found something broken? The PR comment threads (#13744 / #13752) are the best place — the OrcaSlicer maintainers see them too. For things specific to this build / page, the contact form also works.