clippy // help & how it works ← back to home
Pick a task
Quick start 🎀 Record mic & game audio Capture settings Hotkey Storage & options Auto-clip & games Sharing a clip How it works (geeky) Troubleshooting
Need a clip fast? Open clippy, hit Arm, play, then press your hotkey (default Ctrl+Alt+C).

Quick start

1. Install from the home page. (First launch may show a SmartScreen warning β€” see troubleshooting.)
2. clippy opens and auto-arms β€” it's now recording a rolling replay buffer in the background.
3. Play your game. When something cool happens, press your hotkey β€” default Ctrl+Alt+C. The last 30 seconds save to Videos\clippy.
4. Click a clip in the list to play it, or Share to send it to a friend.

🎀 Recording microphone & game audio

By default clippy records video only. Audio is two separate, independent tracks so one can never stall the other. To turn them on, open Settings and scroll to the AUDIO (optional) section:

Microphone (your voice)

1. Tick β€œCapture audio (DirectShow device)”.
2. In Audio device, pick your mic from the dropdown. If it's empty, click the ? button next to it to rescan devices. You can also type a name manually if yours isn't listed.
3. Leave blank = no mic track.

Game / desktop audio (what you hear)

Tick β€œCapture desktop / game audio (what you hear)”. This records your default playback device via WASAPI loopback β€” i.e. the game sound coming out of your speakers. No device to pick; it follows whatever Windows is outputting to.
Good to know: clippy plays inaudible silence on your speakers while recording desktop audio. This is deliberate β€” without it, total silence (e.g. a quiet menu) makes the audio track drift out of sync. You won't hear it.
Track order in saved clips: game/desktop audio first, then microphone. Both are optional and independent β€” enable either, both, or neither.

Capture settings

SettingWhat it doesDefault
Buffer lengthHow many seconds are always kept in the rolling replay buffer. The hotkey saves this much. 15 / 30 / 60 / 12030s
FramerateCapture fps. Higher = smoother but more CPU/GPU. 30 / 60 / 12060
Display to captureWhich monitor to record (0 = primary).0
EncoderVideo encoder. auto picks the best available GPU encoder (NVENC β†’ QuickSync β†’ AMF), falling back to CPU libx264. auto recommendedauto
Quality (CQ/CRF)Constant-quality value. Lower = better + bigger files. 16 β‰ˆ pristine, 28 β‰ˆ small.23
Downscale to 1080pIf your display is bigger than 1080p, cap the recording at 1080p to save resources.off

Hotkey

Save-clip hotkeyThe global key combo that saves a clip from the buffer β€” works inside fullscreen games. Format examples: Ctrl+Alt+C, Shift+F9, Numpad0. Default Ctrl+Alt+C.

Storage & options

Save folderWhere clips are written. Default Videos\clippy. Use … to browse.
Arm capture on startupStart recording the moment clippy opens.
Minimize to tray on closeThe X hides clippy to the system tray instead of quitting (so it keeps recording). Right-click the tray icon β†’ Exit to really quit.

Auto-clip & game integrations

In the AUTO-CLIP section, enable it and pick a Game / method. clippy watches for in-game events and saves clips automatically while armed:

MethodHow it works
auto recommendedDetects the running game (by its window) and switches method automatically. Falls back to OCR when nothing known is running.
OCR (The Finals / Hunt)Reads the screen for trigger words (e.g. eliminated, you died). Use a small Scan region on the kill feed and short, distinctive words for best results. Hit Test now to see what it reads.
War ThunderPolls the game's local telemetry server localhost:8111. Reliably gives match start/end; the 8111 feed is telemetry, not clean kill events. Start a match β†’ Test now to see the live payload and tune an optional trigger regex.
DayZTails your newest .RPT/.log in real time and fires on a regex (e.g. killed|died). Only works if your server writes combat to the client log β€” Test will show what's there.
ValorantReads the local lockfile + presence. Riot's local API exposes match lifecycle (start/end), not real-time kills/deaths.

Timing: scan every (ms) = how often to look; cooldown (sec) = minimum gap between clips from the same trigger (prevents spam while a death screen lingers).

Honest note: these can never be as precise as commercial tools for per-kill/death β€” those use whitelisted memory hooks we can't (and shouldn't, given anti-cheat). OCR + the game APIs are the safe, general methods.

Sharing a clip

1. Click Share on any clip in the list.
2. clippy copies a temporary link (e.g. clippy.neuro-net.net/d/AB3XZ) to your clipboard and shows it in the speech bubble.
3. Send that link to a friend. They open it in a browser β†’ the clip streams straight from your PC (peer-to-peer) β†’ they can play it and download it.
Keep clippy running until your friend finishes the download. The link is temporary and dies when you stop sharing or close clippy. A TURN relay on the server guarantees delivery even through strict NATs. Sharing uses the WebView2 engine, which is preinstalled on Windows 11 (and most Windows 10 PCs).

How it works (the geeky bits)

  • Replay buffer: clippy (via the bundled FFmpeg) continuously captures the screen with DXGI Desktop Duplication (ddagrab) into rotating ~2-second segments. Old segments are auto-deleted so only the last buffer length is ever kept.
  • Save: the hotkey copies the relevant segments out of the live buffer, then muxes them (video + any audio tracks) into an .mp4 with +faststart.
  • Audio: mic and desktop audio are captured by separate processes/streams and aligned by segment index at save time, so neither can stall the others.
  • Encoding: GPU-accelerated where possible (NVENC/QuickSync/AMF), CPU libx264 fallback.
  • Updates: clippy checks this site on launch and applies a small delta patch (only the changed bytes) on next launch.
  • Sharing: a hidden WebView2 page speaks WebRTC; a signaling relay on this server pairs you with the viewer; coturn (TURN/STUN) handles NAT traversal.

Troubleshooting

β€œWindows protected your PC” (SmartScreen)

The installer isn't code-signed (a code-signing certificate costs ~$300/yr). It's safe β€” click More info β†’ Run anyway. It's delivered over HTTPS from this site.

No video / black clip

Make sure the right Display to capture is set and that clippy is armed (green dot, β€œREC ARMED”). Some exclusive-fullscreen games may not capture β€” try borderless/windowed mode.

No audio in clips

Re-check the audio section: mic needs a device picked; desktop audio needs its checkbox on. Clips have two separate tracks (game first, mic second) β€” your player must support multi-track (most do).

Auto-clip never fires

Use the method's Test now button to confirm data is reachable / readable, and tune the trigger words/regex. For OCR, shrink the Scan region to the kill feed and use short, distinctive words.

Share link won't open / download stalls

Keep clippy running and armed. If the friend is on a very strict network, the TURN relay kicks in (slower). They need a modern browser.

← back to home
start
πŸ“– clippy help