System-wide recording
Captures any application, not only browser tabs — desktop tools, spreadsheets, internal clients, the lot.
Record a process once. Wombat captures every click as a screenshot with the instruction already written — “Click Settings”, not “Click here” — then stitches them into a guide you can edit, blur and share.
Click Export
Auto-written from the accessibility layer · zoomed to the target
Documentation usually dies because writing it is a second job. Wombat makes the recording the writing.
Hit record and do the thing you'd otherwise be explaining over someone's shoulder. Wombat shrinks to a small floating pill — invisible to its own screenshots — so it never gets in the shot.
Every click, keystroke and scroll becomes a step: a screenshot zoomed to what you clicked, the control outlined, and the instruction already written from the control's real name.
Reword anything, reorder, drop a step, blur what shouldn't be there, draw an arrow — then export one self-contained HTML file.
Most click recorders can only tell you coordinates, so every step reads “click here” and the reader has to reverse-engineer the screenshot. Wombat asks Windows' accessibility layer what sits under the cursor and names it.
On a spreadsheet-and-dashboard test set, generic “Click here” steps went from 48 out of 48 to zero out of 35.
Full-screen capture means whatever is on screen ends up in the guide. Wombat treats that as the default problem to solve, not an add-on.
Pixelation replaces each block with the average of the pixels it covers — not a downscale that can leave original pixels behind.
Captures any application, not only browser tabs — desktop tools, spreadsheets, internal clients, the lot.
A whole field entry becomes one step with the text that was actually entered — not one step per keystroke.
Each step crops to the control you clicked so it's readable, without ever cropping the stored screenshot. Toggle per step or for the whole guide.
Call out what the automatic marker can't, in your choice of colour and thickness. All of it is burned into the export.
Hide a region as an overlay while you work, then destroy the pixels on disk when you're ready to share.
One file with the images inlined — no folder of assets to lose. A ten-step guide of full-resolution screenshots comes out around 1.5 MB.
Missed something? Wombat hides itself, waits for you to bring the app forward, and inserts a fresh screenshot where you want it.
Drag the click marker, drop a mis-detected outline, rewrite any instruction. The automation is a head start, not a verdict.
Guides are plain files in your user folder. Back them up, sync them, delete them — they're yours.
Free, and free of accounts. Pick your platform — fetching the latest release…
Wombat is a desktop app. Open this page on Windows or macOS to install it.
The normal way in: installs to your user folder, adds a Start-menu entry, and updates itself when a new version ships.
Download for WindowsA single .exe with no installer — for locked-down machines, or a USB stick. It won't auto-update.
Download portable .exeApple silicon by default, with a separate Intel build. Recording, editing, blur and export all work — see the note below on step labels.
Download for macOS
The builds aren't code-signed yet. Windows SmartScreen will say “unknown
publisher” — choose More info → Run anyway. macOS will refuse the first
launch: right-click the app and choose Open, or run
xattr -cr /Applications/Wombat.app. Signing certificates are on the
list; they cost money that this project doesn't take from you.
Smart step labels are Windows-only today. They're built on Windows UI Automation. On macOS every step falls back to generic text like “Click here” — everything else works, but it's the reason the Windows build is the recommended one.
No. Recording, editing, redaction and export all happen on your machine, and guides are stored as plain files in your user folder. The only network request Wombat makes is an update check against its public releases page — and it asks before installing anything.
Anything on screen. Wombat captures the display and hooks input system-wide, so desktop software, spreadsheets and internal clients record exactly like web apps do. Label quality depends on how well an app exposes accessibility information — native Windows and Chromium-based apps are generally good; some canvas-drawn or Java/Qt interfaces expose almost nothing and fall back to generic text.
Password fields are never read: the accessibility helper refuses them at the source, and the step text is redacted again independently, so a value can't leak through either path. For everything else there's manual redaction — drag over a region to pixelate it, and “apply permanently” to rewrite the file so the original pixels are gone. Exports always bake redactions in.
Yes — no account, no trial, no paid tier. It's a desktop app that runs locally, so there's no server bill to pass on.
Because it isn't code-signed. SmartScreen flags any binary from a publisher it doesn't recognise, regardless of what's in it. Choose More info → Run anyway. You can also verify what you downloaded against the checksums on the release page.
Recording, screenshots, the editor, redaction and export all work. Smart step labels don't — they're built on Windows UI Automation, so on macOS every step reads “Click here” until the equivalent native helper is written. macOS also needs Screen Recording and Accessibility permissions granted in System Settings, and the disk image is unsigned, so the first launch needs right-click → Open.
All of it. Rewrite any instruction, reorder or delete steps, insert a step you forgot, drag the click marker to the right spot, drop a mis-detected outline, and toggle the zoom per step or across the whole guide.
A single self-contained HTML file, with every image inlined — so it renders from a mailbox, a shared drive or a wiki attachment with nothing else alongside it. That's deliberately the only format, rather than a half-decent version of four.
Record it once and let Wombat write the guide.