Clients

A Punktfunk host accepts clients over its own punktfunk/1 protocol (the macOS, Linux, Windows, and Android apps) and over GameStream (Moonlight). Pick whichever fits the device you're streaming to. Install a Client has the step-by-step for every device, plus how to update and remove each one.

Two things apply to every app: profiles and punktfunk:// links, and the keys and chords that work while you're streaming. What each app lets you change — resolution, bitrate, codec, HDR, audio, controllers — is catalogued in Client settings.

Apple app (Mac, iPhone, iPad, Apple TV)

The native app for Apple devices speaks Punktfunk's own punktfunk/1 protocol — the lowest-latency, most resilient path, with the full feature set:

• Automatic host discovery — hosts on your network appear under On this network; no IP typing.
• PIN pairing built in, and pinned reconnects after that.
• Controllers, including DualSense — rumble, adaptive triggers, lightbar, motion, and touchpad.
• A game library — browse the host's installed games with cover art and launch one straight into the stream.
• A live stats overlay (resolution, fps, bitrate, latency) and a built-in network speed test to pick a bitrate for your link.
• Widgets, Live Activities and Shortcuts — a hosts widget and a game-library widget for the home screen (the library one opens a picked host's library), a Live Activity while a session runs, and App Intents so Siri and the Shortcuts app can start a stream or jump into a host's game library.

Open the app, pick your host, pair once, and stream. It builds from the clients/apple directory in the repo (Swift / VideoToolbox / Metal).

Moonlight (anything else)

Punktfunk also speaks the GameStream protocol, so any Moonlight client — a browser, a smart TV, an old phone, a games console — connects with no punktfunk-specific software; it's the catch-all where no native Punktfunk app exists. See Connect with Moonlight. It gets encrypted video, error correction and host-side adaptation to a lossy link like the native clients do; what it doesn't get are the native protocol's extensions (client-side speed test, jumbo frames).

Linux desktop client (GTK4)

punktfunk-client is the native graphical Linux client — a GTK4 / libadwaita app that speaks punktfunk/1 directly, with vendor-ordered hardware decode (Vulkan Video first on NVIDIA and AMD, VAAPI dmabuf first on Intel; whichever isn't first is the fallback, and software decode is last), PipeWire audio, and SDL3 controllers (rumble, lightbar, DualSense touchpad/motion). The decoders are Punktfunk's own — nothing here links FFmpeg, and they talk to your GPU's Vulkan and VAAPI drivers directly. To force one, pick it in Preferences → Display → Video decoder or set PUNKTFUNK_DECODER=native-vulkan|native-vaapi|software. Like the Apple app it discovers hosts automatically, does PIN pairing, pins reconnects, and browses the host's game library (with cover art) to launch a title straight into the stream.

It ships as real packages — full steps in Install a Client:

• Any Flatpak distro (recommended) — one command from the hosted flatpak.unom.io repo (exact command and update flow in the guide above). It's also the client the Decky plugin uses by default, though the plugin drives a native punktfunk-client just as well.
• Ubuntu 26.04 or newer — apt install punktfunk-client from the Punktfunk apt registry. The client package needs SDL3 and GTK4 ≥ 4.20, which Ubuntu 24.04 LTS doesn't ship — on 24.04 use the Flatpak.
• Fedora — sudo dnf install punktfunk-client from the Gitea RPM registry (add the repo as in the Fedora guide).
• Fedora Atomic / Bazzite — use the Flatpak. rpm-ostree install punktfunk-client works, but layering slows every OS update, so it's a last resort on an image-based system (see Bazzite).
• Arch — sudo pacman -Syu punktfunk-client from the signed binary repo (see Arch Linux).

Launch it, pick your host from the list, and stream. For scripting, use the punktfunk CLI that ships in the same packages:

punktfunk launch <host-ref>              # start a session, waking the host first if it's asleep
punktfunk-client --connect <host>:9777   # the older flag — still supported for existing scripts

Couch mode. The same client also has a gamepad console UI: a full-screen, controller-driven front end with the host list, PIN pairing, settings, Wake-on-LAN and the game library, streaming in its own window. Three ways in — the gamepad button in the shell's header bar (also Main menu → Console UI), the separate Punktfunk Console launcher the packages install alongside the app, or:

punktfunk-client --browse --fullscreen

The client also updates itself (punktfunk-client --check-update / --apply-update) — see Keeping a client up to date.

Android app (phone + Android TV)

The native Android app speaks punktfunk/1 directly, on phones and Android TV. It does hardware HEVC decode (including HDR10), Opus audio with a mic uplink, game controllers with rumble and DualSense feedback, automatic host discovery, PIN pairing with pinned reconnects, the host's game library with cover art, and a live stats overlay — with D-pad and game-controller focus navigation for the couch. It builds from the clients/android directory (Kotlin + a shared Rust core).

Controllers. Plug a DualSense, DualSense Edge or DualShock 4 into the phone or tablet by USB and grant the USB permission Android asks for — Punktfunk then drives the pad itself instead of taking what Android's gamepad layer exposes, so the host gets rumble, adaptive triggers, the lightbar and gyro. The app's Controllers screen lists attached pads and their capture state; the switch that turns this off is DualSense / DualShock passthrough (USB) in Settings. Over Bluetooth the pad still works as an ordinary gamepad, but adaptive triggers and the lightbar need USB.

The app is on Google Play as a public listing — no invite — or sideload the public APK (see Install a Client); canary builds ride a separate, invite-only Play Internal testing track. Open the app, pick your host, pair once, and stream.

Windows desktop client

punktfunk-client for Windows (clients/windows) is the native graphical client — pure Rust, the same punktfunk/1 core as the Apple, Linux, and Android apps, with a WinUI 3 UI (host list, settings, PIN pairing); the stream itself runs in Punktfunk's Vulkan presenter. Decoder order is per-vendor: Vulkan Video, then D3D11VA, then software on NVIDIA and AMD, and D3D11VA first on Intel and other GPUs (Intel's driver advertises Vulkan Video, but DXVA is the proven path there). It has 10-bit/HDR present, WASAPI audio + mic, SDL3 controllers (rumble, lightbar, DualSense), network discovery, the host's game library with cover art, and the full PIN-pairing trust surface. It builds for x86_64 and aarch64 and ships as a signed installer (plus a portable zip, and an MSIX for Microsoft Store compatibility).

The package installs two Start-menu entries — Punktfunk, the desktop window, and Punktfunk Console, a controller-driven fullscreen interface for a TV or HTPC (host list, pairing, settings and game library, all navigable with a pad) — plus the headless punktfunk command on your PATH.

Hardware decode and HDR10 present are validated on glass on NVIDIA and Intel (including HDR pass-through on the Intel D3D11VA path). If anything misbehaves, Moonlight is a proven alternative for Windows.

For scripting, prefer the punktfunk CLI. The window binary's own headless flags stay supported:

punktfunk-client                                              # open the WinUI 3 window (host list / settings)
punktfunk-client --discover                                  # list hosts on the network
punktfunk-client --headless --speed-test --connect <host>:9777  # no window: probe the link, print measured/recommended bitrate

webOS (LG TV) — community

pf-webos is a native client for LG webOS TVs, built and maintained by the community (dyptan-io) on Punktfunk's punktfunk/1 protocol and core. It's not an official Punktfunk app, but it speaks the real protocol directly (not Moonlight/GameStream) — LAN discovery or add-by-IP, PIN pairing with pinned reconnects, hardware video decode via webOS's NDL DirectMedia API, and a browsable game library with cover art, navigable with the Magic Remote.

It ships as a sideloadable .ipk (homebrew package) rather than through the LG Content Store — see Install a Client for the sideload steps.

Scripting: the punktfunk CLI

punktfunk is the headless client — the same core the graphical apps use, with no window. It ships in every Linux client package (apt, dnf, pacman and the Flatpak) and in the Windows installer, so if you have a desktop client you already have it:

punktfunk hosts list --probe                  # saved hosts, each with a live reachability check
punktfunk pair <host>[:port] --pin -          # enrol this device with a host (PIN on stdin)
punktfunk library <host-ref> --json           # the host's games, machine-readable
punktfunk launch <host-ref> --game <id>       # stream, waking the host first if it's asleep
punktfunk open 'punktfunk://connect/<host-ref>'
punktfunk speed-test <host-ref>               # measure the link, print the recommended bitrate

A <host-ref> is a saved host's id, its name, or an address — the same reference a punktfunk:// link takes. There is also hosts add / hosts forget, wake, reachable, profiles list and reset; run punktfunk help <command> for a verb's flags.

--pin - reads the PIN from stdin (echo 1234 | punktfunk pair …), which is the form to script. --pin 1234 still works, but the value sits on the command line, where every local user can read it (/proc/*/cmdline); with neither flag, an interactive run asks for it.

punktfunk open connects on its own only when the link names its host by the stable record id. A link naming it by label or address is a guess anything could make, so it asks first — and with no terminal to ask on it refuses (exit 6) unless you pass --yes.

Exit codes are stable, so a script can branch without parsing prose: 0 ok, 2 connect failed, 3 trust rejected (re-pair), 4 the renderer couldn't start, 5 nothing matched what you named, 6 it needs a person (pairing, or an unknown host).

Under the Flatpak, run it as flatpak run --command=punktfunk io.unom.Punktfunk <args>.

The older punktfunk-client --connect, --discover and --headless --speed-test flags stay supported on Linux and Windows for existing scripts, but build new things on punktfunk: it wakes a sleeping host before connecting, which those never did.

punktfunk-probe is different again — an in-repo protocol test and latency-measurement tool for development, not shipped in any package; you build it from source.

Profiles and links (every app)

Two things work the same in the Apple, Linux, Windows and Android apps. Settings profiles are named sets of stream overrides — bitrate, resolution, codec, HDR and the rest — that you bind to a host or pick for a single connect; every field you didn't touch still follows your defaults. A punktfunk:// link starts a stream from a browser, a desktop shortcut, a home-automation rule or punktfunk open, carrying only references to things that already exist on your device — never a setting, never a trust decision.

Profiles and links has both in full: the link grammar, where each app puts Copy link and Create shortcut…, and what a link is refused for. From a script, punktfunk profiles list and punktfunk launch --profile <ref> reach the same profiles.

While you're streaming

Click the stream and the desktop clients capture your keyboard and mouse — everything goes to the host until you let go. Ctrl+Alt+Shift+Q (⌃⌥⇧Q or ⌘⎋ on a Mac) gives it back.

That chord, the three others a stream reserves, the controller chord that needs no keyboard, which app honours which, the two mouse modes, the three touch modes and stylus input are all on Mouse, touch and pen.

Copying between the two machines is a separate opt-in: the host operator allows it in host.env and you turn it on per host in your client. Content crosses today from the macOS, iOS, iPadOS, Windows and Android apps — the Linux client has the switch but no bridge behind it yet, and tvOS has no pasteboard to share. See Shared clipboard.

Which should I use?

Whichever you choose, the first connection needs a one-time pairing.