Let's get you set up.

A few quick steps and Huntlog will start logging your matches automatically.

1

Share your game window

Pick the Hunt window when prompted so Huntlog can watch the screen.

Not shared yet
2

Capture the end-of-match screen

The summary is the screen you see right after a match ends, showing your bounty, kills, and rewards. Open it in-game, then press and hold the button below to set it as Huntlog's reference.

Not captured
3
Using Huntlog in a match

Keep Huntlog open in a browser tab while you play. When a match ends:
- Open the end-of-match summary and let it fully load. Bounty, kills, and rewards all need to be on screen.
- Huntlog detects the screen and walks through each row. You'll see a progress overlay on this site while it reads.
- When it finishes, the match is saved to your history on this page.
- If it misses a match, open Settings → Tools and click Extract summary now while the summary is still on screen.
4

Play a sound when a match is saved

Optional. A short chime plays the moment Huntlog finishes saving, so you don't have to watch the progress bar.

Play a sound when a match is saved
5

Back up your history (optional)

Huntlog stores everything in your browser. Clearing site data wipes your history. Pick a folder and Huntlog will drop a daily zip into it so your matches stay safe.

Not configured

Tip: point it at a folder inside Google Drive / Dropbox / OneDrive and you'll have cloud backup for free.

Complete steps 1 and 2 first

How Huntlog works

In plain words, for people who just want to know what this thing is doing on their computer.

The short version

Huntlog watches the window you share with it, waits for the end-of-match summary screen to appear, reads the numbers off that screen, and saves them to a list of your recent matches. That's it.

Step by step

1

You pick a window to share

When you click Start watching, your browser (not Huntlog) asks you which window to share. You pick Hunt: Showdown. Huntlog never sees anything else on your screen.
2

It looks for the summary screen

A few times per second, Huntlog takes a tiny thumbnail of the shared window and compares its colors to the reference summary screen you captured during setup. If the colors look close enough, it figures the summary is showing.
3

It reads the numbers with OCR

Once the summary is up and stable, Huntlog runs Tesseract, an old-school text recognition library, on the screenshot to pull out numbers like bounty, kills, and money. Same idea as your phone recognizing text in a photo.
4

It saves the match in your browser

The extracted numbers get stored in your browser, on your machine. Your match data never leaves your browser.

Why it can't do anything sketchy

Huntlog is a client-side web app. That's a technical phrase, but the meaning is simple: everything you see happens inside your browser, on your machine. There is no Huntlog server. Your match data never leaves your browser, because we didn't build anywhere to send it to.

It can't read your game files. A browser tab is not allowed to touch files on your disk. Not game folders, not save files, not logs.
It can't read game memory. Browsers have no ability to inspect another program's memory. Huntlog literally cannot see inside Hunt: Showdown.
It's not a mod, trainer, or cheat. It doesn't inject anything, doesn't hook into the game, doesn't modify files. From the game's perspective, Huntlog doesn't exist.
It only sees the window you pick. Screen sharing is a standard browser feature (the same one video calls use). You choose the window, and you can stop sharing any time.
Your match history stays on your computer. It's saved by your browser, on your machine. Clearing your browser data wipes it. The Delete all matches button in settings wipes it too.
Your matches stay on your machine. No account, no sign-in, no match data uploaded. We do use Betterlytics (a privacy-first, cookieless analytics service) for anonymous pageviews and a handful of aggregate counts, like how often matches get extracted. Nothing tied to you or your history.

Don't take our word for it

If you're the paranoid type (good on you), here's how to check:

Open your browser's DevTools (usually F12) before you start a session. The Network tab lists every request the page makes. You'll see the initial page load, plus the occasional small ping to betterlytics.io for anonymous usage counts. No match data going anywhere.
Still in DevTools, the Sources tab lets you read the client-side files Huntlog actually runs. They're minified, but the shape of what's happening is there to see.
Turn off your Wi-Fi after the page has loaded. Capture, OCR, and saving all run entirely in your browser, so Huntlog keeps working. The analytics pings just fail silently.

The catch

OCR isn't magic. Sometimes it misreads a number: a 0 as an 8, a 7 as a 1. That's why every stat on a match card is editable. Click the little pencil and fix it. Your history is yours.

Let's get you set up.

Share your game window

Capture the end-of-match screen

Using Huntlog in a match

Play a sound when a match is saved

Back up your history (optional)

Your Hunt stats, automatically.

How Huntlog works

The short version

Step by step

You pick a window to share

It looks for the summary screen

It reads the numbers with OCR

It saves the match in your browser

Why it can't do anything sketchy

Don't take our word for it

The catch