Setting up OBS: capture the overlay + WebSocket
Zappify has no browser sources and no per-module URLs. Instead every overlay module renders into one shared transparent window ("Zappify - Overlay") that you add once as a Window Capture in OBS. Separately, Zappify uses the WebSocket server built into OBS (v5) to control scenes, sources and audio and to detect a running recording — the basis for ClipModule, ReplayModule and the facecam controls. The initial setup wizard can automatically create the overlay's window capture in OBS on first launch and scale it to canvas size. For OBS filters (e.g. blur) that should show/hide in sync with a module, there's a central "OBS Filters" tab instead of settings scattered across each module. New in 1.0.19: The overlay renders at your OBS canvas resolution (e.g. 2560×1440 or 4K) instead of being upscaled. On connect, Zappify reads the base resolution, resizes the overlay window (Windows scaling is taken into account) and fits the source back to the full canvas. Can be turned off in Settings under “Match OBS canvas size automatically”. The overlay intentionally stays a window capture (not a browser source) because many displays need Zappify-internal features; the ready check on Home detects typical window-capture pitfalls. New in 1.0.20: "Create automatically in OBS" in the setup wizard also creates the audio source "Zappify Ton" (application audio capture) and adds it to every scene that contains the overlay. Alerts, TTS, sounds and music can then be controlled in OBS separately from desktop audio. The startup check verifies the source in its own "Zappify audio" row and offers a fix button if it is missing, captures the wrong audio or Zappify is captured twice. Since 1.0.24: if OBS doesn’t answer under load Zappify aborts the command after 5 s (screenshots 10 s) – automation rules keep running; after three missed replies the connection is rebuilt.
Trigger Add the Window Capture once in OBS; connect the WebSocket once in the control panel under Settings → OBS.
Requirements
- OBS Studio 28 or newer (WebSocket v5 is already built in).
- Zappify is running. The overlay window starts with it and sits off-screen until a module shows something.
- For the WebSocket: OBS and Zappify on the same machine (or one reachable on the network). The Window Capture itself only works locally on the Zappify PC.
- The only real browser source is the optional facecam frame — its URL is in the Facecam tab.
Step by step
- Capture the overlay: in OBS add a "Window Capture" source and pick the "Zappify - Overlay" window.
- Set the capture method to "Windows 10 (1903 and later)" / "Windows Graphics Capture" — only that preserves transparency and captures the off-screen window.
- Size the source to 1920×1080 and keep it on top in the scene. You position individual modules in the Positions tab in Zappify, not in OBS.
- WebSocket (optional, for clips, replay, facecam control, audio mixer): in OBS open Tools → WebSocket Server Settings, tick "Enable WebSocket server", note the port (default 4455), optionally set authentication + password.
- In the control panel under Settings → OBS enter host (localhost), port and password and click "Connect" — the status switches to "connected".
- Optional: tick "Control audio via OBS" to adjust overlay volume separately in the OBS mixer.
- Some modules open their own window (THE DROP, infection game, replay slider, Screen Picker) — add a separate Window Capture for each if you want to show it.
If it doesn't work
- Window Capture is black or opaque: switch the capture method to "Windows Graphics Capture" — the older BitBlt method does not reliably capture the frameless transparent window.
- "Zappify - Overlay" missing from the window list: Zappify must be running and the window must have shown something at least once — trigger it from the Positions tab or a module test.
- "Connection refused" (WebSocket): the server in OBS is off or the port is wrong.
- "Authentication failed": wrong password — reveal it again in OBS and copy it exactly.
- Different machine: in Zappify's OBS settings use the LAN IP instead of localhost and allow port 4455 through the firewall. That only covers the WebSocket — the overlay cannot be pulled into an OBS on a second PC over the network.
- Overlay black instead of transparent or with jagged edges: the window capture uses BitBlt. On Home under “Ready to go?” click “Reassign” – Zappify switches to Windows Graphics Capture.
- Overlay blurry at 1440p/4K: check that “Match OBS canvas size automatically” is on and click “Adjust” in the ready-check row “Overlay resolution”.
- Alerts are heard twice or too loud: Zappify is also captured through desktop audio or the "Capture audio" option of a window capture. Mute desktop audio and add your game/Discord via application audio capture. The audio source requires OBS 28 and Windows 10 (2004) or newer.
Last updated: 7 November 2026