Your ERP isn’t a browser tab.
Neither is your recorder.
Browser extensions can't see your desktop apps; Spawnit can. It records the desktop tool nobody will rewrite. Steps carry the button or field name where the app exposes one; otherwise you get the screenshot and the click position. It does not add a special path for remote-desktop software.
Free plan at launch.
A page recorder can only record a page.
Browser extensions attach to a tab and read its DOM. That covers the SaaS half of your day and none of the rest of it.
A session inside a terminal emulator. The in-house front end that has run finance since before any of this was a web app. None of it is a tab, so none of it is visible to a tool that lives in one.
Spawnit records the window, because it records the desktop. What changes from window to window is not whether it records — on the display you picked, it always does — but how much of that window the system will describe.
From the appA fat client installed from an MSI is recorded the same way. Steps carry the real button or field name, including AutomationId, where the app exposes one through UI Automation. Otherwise you get the screenshot and the click position.
- Global click, scroll and key-press capture, system-wide.
- A screenshot at every step, pulled from the live capture stream.
- the window title and process name behind each step, where the app reports them.
- One share link at the end. Viewers need no account.
One task: post a vendor invoice against its PO.
Six steps in an ERP client, recorded once. The step your teammate reads sits on top; the raw line Spawnit logged sits underneath — including the step the ERP refused to name.
- 1
Open Accounts Payable, then Vendor Invoices
click → menu item "Vendor Invoices"
menu item · Accounts Payable
- 2
Enter the purchase order number
key press → edit "PO Number"
edit · Invoice Header
- 3
Select the receipt line in the match grid
click → (742, 318)
no accessible name — coordinates and screenshot only
- 4
Run the three-way match
click → button "Match to receipt"
button · Matching
- 5
Tick Release for payment
click → check box "Release for payment"
check box · Payment terms
- 6
Post the invoice
click → button "Post"
button · toolbar
Step 3 is the honest one. That grid cell publishes no accessible name, so Spawnit logged coordinates and a screenshot rather than inventing a label.
The step still works — it shows the screen. What is missing is the control name in the log line: step 3 carries coordinates where the other five carry a label. That is a property of the application, not of the recorder, so the honest thing is to show you the step where it happened.
What you always get, and what depends on the app.
Sorted by what the app exposes, not by vendor — there is no per-app profile in the product and no support matrix behind this page.
Every window on the display you pick
A still screenshot at each click, the click coordinates, key presses and scrolls, the window title and the executable behind it. There is no video. the bounds include one display per session, and never the secure desktop.
Where the app publishes a UI Automation provider
The control's visible label, its type, its AutomationId and its bounding box — what turns a click at (742, 318) into a step reading button “Post”. The application decides whether it publishes any of that. Spawnit ships a uia-audit command, so the first thing you do with the build is measure your own app on your own machine.
Spawnit publishes no coverage percentage for anyone’s software, because no measurement exists to publish. uia-audit is there so the number you use is one you measured on your own machine.
Desktop and legacy apps are ordinary windows on the computer you record. Spawnit logs the clicks and keypresses and takes a still at each step. a control is named only where that application publishes a name. There is no remote-desktop-specific capture.
The questions an IT reviewer asks first.
Answered from what the capture client does today, limits included.
Our ERP screens show customer and payroll data. What lands on disk?
Captures stay on your own computer, and nothing uploads unless you sign in and enable sync. By default, sessions are purged once their newest file is 14 days old, with two exceptions worth knowing: a session still being written is never purged, and if you have enabled sync, a session that has not uploaded yet is kept, because the local copy is the only copy. No audio, microphone or webcam capture exists anywhere in the app, and there is no telemetry SDK in the client. Stated plainly: the on-screen labels and window titles of what you click are stored as plain text in the local event log.
Are password fields protected?
Best-effort, and here is what that means. A field the app marks as a password gets its rectangle painted solid black in the step screenshot before that screenshot is used for anything, and key presses into it become [redacted]. Black rather than blur is deliberate: deterministic, and unmistakable to whoever reviews the guide. The limits are real — the scan covers the foreground window, it is time-bounded, and it is skipped entirely on a machine auto-detected as low-memory (under 4 GB of RAM, or two or fewer cores). Spawnit does not capture video. Each step is a still screenshot.
Does it need admin rights, or slow the machine down?
It installs per user, never asks for elevation, and its logon task runs at least-privilege with below-normal priority. The input hook does no work in its callback: it hands events off and drops them rather than stall system input, so capture is deliberately lossy under load rather than deliberately complete. Auto-start is not hidden — the installer registers a logon task and makes you tick a consent page itemizing what is captured.
Where can it not see?
Elevation prompts and the sign-in screen are off-limits to the recorder by design. A window the system keeps at a higher privilege than Spawnit reports no title and no process name. Some antivirus and game-mode software interferes with input hooks. And one display is recorded per session — you pick which.
Can I exclude a specific application from capture?
Today only from the command line, via the app and window-title denylists; the desktop app ships both empty with no setting to fill them. private-browsing windows whose titles carry InPrivate, Incognito, or Private Browsing are dropped whole, and any observation Spawnit cannot attribute to an application is dropped rather than kept.
Documenting something else?
Answer the same ticket once, then send the link
Record the fix while you are already doing it, then the next person follows the guide.
IT & helpdeskOps & site leadsStandardise the process on a recording, not a rewrite
Record the task once. The guide is what the team follows. When the task changes, record it again.
OperationsPeople & team leadsOnboard from real work, not last year's slide deck
A new hire follows the guide. Button and field names come from the app's interface, where the app exposes one.
HR, onboarding & trainingUse casesThe other things teams record first
Onboarding, vacation handoffs, helpdesk answers and the SOP that keeps getting postponed — five jobs, one link each.
Browse use casesPlansWhat this costs a team
Capture, per-step screenshots and share links are on every plan — up to 10 guides on the free plan at launch, unlimited on Pro. Pro and Team pricing is being finalized.
See pricingTry it against your worst screen
The useful test is not the demo app — it is the oldest window in your estate. Leave your email and we will send the Windows build the moment it opens, so you can run uia-audit against that window yourself.