01Before you start
KillFeed reads the text on your HUD. If the text is not in the recording, there is nothing to read.
You need Windows 10 or 11, and WARDOGS recordings from any tool — OBS, NVIDIA ShadowPlay, Medal, Aitum Vertical, Xbox Game Bar. Three things matter about those recordings:
- 1080p or 1440p. The text zones are measured as fractions of the frame, so any 16:9 resolution works, but these two are what the alpha is tuned on.
- HUD scale at 100 %. Below that the kill banner shrinks out of the zone KillFeed reads and kills start going missing.
- The whole game window. If you crop your capture, crop from the edges, not around the crosshair.
You do not need to record at high quality. KillFeed only needs to read text and cut 15–30 second pieces, and YouTube re-encodes everything you upload anyway. If your recordings are eating your disk, turn the quality down before you turn anything else down — on NVENC, CQP 23–24 is usually indistinguishable from CQP 20 once it has been through YouTube, at roughly half the size.
No recordings yet? The app has a built-in recording guide with the exact menu paths for OBS, ShadowPlay and Medal. It is the link on the first page of the setup wizard: No recordings yet? How to set up OBS / ShadowPlay / Medal.
02First run: four questions
There is no installer. Double-click KillFeed.exe and the wizard opens. Windows SmartScreen warns once because the alpha is not code-signed — More info → Run anyway.
Where are your recordings?
Point at the folder your recording tool writes to. Sub-folders are searched two levels deep, so Videos\ works if everything lives under it.
If you record vertical clips separately — Aitum Vertical, for example — tick I also record ready-made vertical 9:16 and give that folder too. When the same kill exists in both, KillFeed keeps the vertical one, because it is already the right shape.
Use Test: how many recordings will it find? before moving on. It tells you the count and roughly how long a full pass will take.
What should KillFeed make?
Shorts, recaps, or both. Recaps are off to one side of the main job: a chronological 16:9 summary of the day, built from your normal recordings once enough has collected. If you only want clips to post, leave recaps off — it is less work for your PC.
What is good enough to publish?
This is the one that decides how much lands in Publish\:
- Multikills and vehicle kills — the default, and what the channel data supports.
- Multikills only — two or more kills in the same clip, nothing else.
- Every kill — everything goes to Publish and you sort it yourself.
You can change this later without losing anything. When you do, KillFeed moves the clips you already have between Publish\ and Other\ to match the new rule, rather than only applying it to the next thing it cuts.
Where should the finished clips go?
Either next to your recordings, or in a folder that syncs to your phone — OneDrive, Google Drive, Dropbox. The second option is the reason most people post from the YouTube app ten minutes after a session: the clip is already on the phone.
KillFeed creates Publish\, Other\ and Recaps\ itself when there is something to put in them.
Tick Start KillFeed with Windows and press Start KillFeed. That is the whole setup.
03The first pass takes hours. That is normal.
Reading text out of video is slow. Everything after the first pass is fast, because each recording is only ever read once.
Reckon on roughly 20 to 30 minutes per hour of recording. A folder with a week of evening sessions in it is an overnight job. You can use the PC normally while it runs: ffmpeg and Tesseract run at idle priority, which on Windows also means low disk priority, so they step aside for anything else that wants the machine.
KillFeed will not start clipping while the game is open, and if you launch the game in the middle of a run it stops within five seconds — the recording it was on is clipped again from the start next time. Reading video is heavy enough that it will take frames off a game if both run at once, so it does not try to share.
If you would rather clip while you play, three values in settings.json control how much of the machine clipping may use. cpu.workers is how many text-reading processes run at once — half your logical CPUs by default. cpu.worker_cores pins the work to chosen cores, which on an Intel 12th-gen or newer means you can put it on the E-cores and leave the P-cores to the game: "16-31". And cpu.hwaccel: "cuda" moves video decoding to the GPU's own decoder block, which is the single biggest saving — but test it on one recording first and check you get the same number of clips.
After that first pass, a session is clipped in the time it takes to read it once, usually while you are still winding down.
"Nothing new" right after a session is expected. KillFeed leaves a file alone until it has stopped growing and is at least two minutes old, so it never reads a recording that is still being written. Give it a couple of minutes and press Run now again.
04What lands where
Four folders, and a page you open in your browser.
Every clip comes with a .txt next to it holding a ready-made title, and a .json with what KillFeed saw — kills, vehicles, distance, the clock time of each event. Post the mp4, paste the title, done.
RecapBank deserves a word, because it is not obvious. The recap is cut from your original recording, not from the finished shorts. That means deleting recordings to save space would quietly delete kills out of every future recap. So while KillFeed is clipping, it also saves the recap-sized pieces as small separate files — under a gigabyte per session, against tens of gigabytes for the recording. Once a session is in the bank, the recording is no longer needed for anything.
05The Dashboard
KillFeed lives in the tray next to the clock. On Windows 11 the icon usually hides under the ^ arrow — click that to find it. Right-click the icon to open or quit.
| Control | What it does |
|---|---|
| Run now | Checks for new recordings immediately instead of waiting for the next minute. During a run this button becomes Stop after this file, then Stop now. |
| Pause | Stops picking up new work without forgetting anything. Useful if you want the CPU back. |
| Make recap now | Builds a recap from whatever has collected, even if it is below the minimum length. |
| Browse clips | Builds a page of every clip with thumbnails and opens it in your browser. This is where you mark the good ones — see below. |
| Recent clips | The list at the bottom. Double-click to play. Right-click for two useful things. |
Those two right-click options are worth knowing:
- Why is it in this folder? — states the rule, the clip's own numbers, and the verdict, in three lines. If you ever disagree with where a clip landed, start here.
- Re-clip the recording it came from — reads that recording again with your current settings. The clips it already made stay on disk, but they leave the app's list.
06Picking the good ones
The one judgement in the whole pipeline that is not a formula.
Press Browse clips and you get a page of every clip with a thumbnail, its kills, distance and length, sortable and searchable. Each clip has two buttons: ▲ and ▼.
- ▲ worth posting — jumps to the front of the queue, and gets posted even if it would not otherwise have passed your rule.
- ▼ never post this — never uploaded, by anything, ever.
Two filters at the top, Marked ▲ and Marked ▼, show what you have decided so far.
This exists because of something worth being straight about: KillFeed cannot tell a good clip from a lucky one. It counts kills, vehicles, distance and seconds, and none of those reliably predict whether anyone watches. The score sorts the queue into a sensible order and keeps the empty ones out. Which of the survivors is actually worth posting is a judgement, and you are the one who can make it.
Open it from the app, not from the folder. The page saves your marks by talking to KillFeed itself, over a small server that only listens on your own machine. Opened straight off disk — or from your phone after syncing — the page still works, but the buttons will tell you they cannot save.
07Tuning what gets cut
Advanced tab. Every value takes effect on the next run, and the ones marked below also re-sort the clips you already have.
Shorts
| Setting | What it changes |
|---|---|
| Seconds before the kill | The lead-in. 8 s by default. Helicopter players often want less, infantry players more — this is the single setting most worth experimenting with. |
| Seconds after the last kill | The tail. 3 s is usually enough; the kill is the payoff, not what follows it. |
| Minimum / maximum short length | 15 to 30 seconds. Viewers watch about 17–23 seconds whatever the length, so longer mostly costs you. |
| Kills must be within N s of each other | What counts as a burst. Two kills twenty seconds apart make a long clip where nothing happens in the middle — those go to Other\ instead. |
| Skip a lone kill with nothing within N s | A single kill standing on its own is not cut at all. On a typical session that is three quarters of everything KillFeed would otherwise produce, and none of it could reach Publish anyway. A kill and the vehicle it destroyed count as one moment together, so those are kept — as is a vehicle kill on its own. |
Turning 16:9 into 9:16
Three ways, under How 16:9 recordings become 9:16:
- Centre crop — sharp, fills the frame, shows the area around your crosshair. The default.
- Blurred background — the whole picture, with the sides filled in. Nothing is cut off, but the gameplay appears smaller.
- Split — the whole picture across the top, and a zoomed centre crop below it. You keep the HUD and the kill feed readable and still get the action large. Worth trying if you have no vertical recording of a moment.
If you record vertical clips separately, none of this applies to those — they go through untouched.
Scoring
Clips are ordered by 1 point a kill + 2 a vehicle + 1 per 100 m − half a point a second over 22. It is an ordering you can do in your head, not a prediction. Anything you mark ▲ goes in front of all of it.
Destroying an occupied vehicle shows two banners at once — a kill and a vehicle destroyed — but it counts as one thing worth 2, not two things worth 3. Otherwise a single vehicle kill would tie with a three-kill streak, and the streak is the better clip. It is named once in the title for the same reason.
08The recap
A chronological 16:9 summary of your kills, cut from your normal recordings.
It builds itself once enough has collected — between the minimum and maximum length you set — or immediately when you press Make recap now. The settings worth knowing:
| Minimum kills for a clip to be included | Raise this to 2 and the recap becomes a highlight reel instead of a log. On a typical session it cuts about 80 % of the material. |
| Use recordings from the last N days | How far back it looks for material it has not used yet. |
| Seconds before / after each kill | Tighter than the shorts settings, because the clips are strung together. |
Be honest with yourself about whether you want one. A ten-minute recap is a different kind of video from a short, and it competes for attention against everything else on the platform rather than in the Shorts feed. If it is not getting watched, the answer is usually to raise the minimum kills until it is short enough to be a Short, not to make more of them.
09Disk space
Recordings are tens of gigabytes. The clips made from them are tens of megabytes. That gap is where all your disk goes.
Under Advanced → Disk space there are three settings, and they only make sense together:
| Setting | What it means |
|---|---|
| Delete the recording once it has been clipped | Off by default. When on, the original is deleted after KillFeed has finished with it. |
| …but keep it until its kills have been used in a recap | The brake. With this on, a recording stays until the recap no longer needs it. |
| Keep the recap pieces as separate small files | On by default. Once a session is in the bank, the recap does not need the recording any more — so this is what makes deleting safe. |
This cannot be undone. A deleted recording does not go to the Recycle Bin. Before you turn it on, let one full pass finish with it off, look at the clips it made, and satisfy yourself that the detection is finding what you expect. Then turn it on.
KillFeed will not delete a recording it failed to clip, and it will not delete one where it read no kill text at all — a session that looks completely empty is far more likely to mean something is wrong with the setup than that nothing happened.
There is also Delete clips in Other\ after N days, which is a much smaller and much safer lever: those are clips you have already decided not to post.
10When it looks wrong
Most problems are one of five things.
It found no kills at all
Almost always the HUD. Check it is at 100 % scale and that your capture includes the whole game window. Then check the resolution is 16:9 — an ultrawide recording puts the kill banner somewhere KillFeed is not looking.
If a single recording fails but others work, that recording may be damaged or still writing. Try playing it.
A clip says one kill but there are clearly two
Two kills in a row overlap on screen: the second banner replaces the first with no dark frame between them. KillFeed tells them apart by the reward printed inside the banner. If the amounts happen to be identical it can still merge them — rare, and deliberately preferred over inventing kills that did not happen.
A clip has no kill in it
Only the banner under your crosshair can create a kill. The money counter and the kill feed down the left side show what everyone on the server is doing, and both are outside the 9:16 crop — they contribute distance and amounts, never events. If you see a clip with nothing in it, that is a bug worth reporting, with the clip.
Good clips are landing in Other\
Right-click the clip and choose Why is it in this folder? — it will tell you which rule it failed. Usually it is either the burst rule (kills too far apart) or the publish rule. Change the setting and KillFeed will move the existing clips to match.
Everything is slow, or the disk fills up
Lower your recording quality first — it is almost always the cause, and it costs you nothing visible. Then turn on Skip a lone kill if it is off, which removes most of the clipping work. Deleting recordings is the last lever, not the first.
Something else
Press Send feedback in the app. It puts a zip on your desktop with the log and the text KillFeed read — never any video. Drop it in #feedback on Discord with your resolution, recording tool and class.
KILLFEED