User guide

Everything from a fresh install to a finished tutorial.

You do a task once. DigiRecord watches, and turns what you did into documentation and automation. It captures clicks, typing and navigation inside a browser built into the app, or records any window or region of your screen. Nothing is uploaded — everything stays on your computer.

Your first recording

1. Open the recorder. From the home screen, choose Record a Browser Flow, or press Ctrl+N.

2. Go to your starting page. Type the address into the URL bar and press Go. Anything you do before you press record is not captured, so this is the moment to log in, dismiss cookie banners, and get to a clean starting point.

3. Decide about screenshots. The Screenshots checkbox captures a picture with every step. Leave it on if a person will read the result, because the screenshots are what make it readable. Turn it off if you only want a Playwright script, and recording will be faster.

4. Press Record and do the task exactly as you normally would. Clicks, typing and navigation are all captured. Work at a normal pace; there is no need to pause between actions.

A note on passwords. Text you type is recorded, including into password fields. Log in first, then start recording.

5. Press Stop (Ctrl+S). You land on the review screen.

Reviewing what you captured

Nothing is produced until you say so. The review screen lists every step in order with its screenshot, and this is where you fix what the recording got wrong. You can rename a step, so “Click #submit-btn” becomes “Submit the expense claim”. You can rewrite a description to add context the recording could not know. And you can hide a step, so a mis-click or a detour never reaches the finished guide.

Spend a minute here. It is the difference between a transcript and a document someone can follow.

The four things you can produce

Save as Flow stores the recording in your library so you can replay it or generate different outputs later. It does not produce a document. If you want to keep the recording at all, do this.

Generate Tutorial produces a step by step HTML guide with your screenshots and descriptions. It is a self contained page you can open anywhere, send to someone, or host.

Export as PDF renders the same guide as a document, for onboarding packs, audits, and anyone who prefers a file to a link.

Export as Playwright turns the recording into a runnable script. It prefers stable selectors: an element id first, then a test attribute or name, then an accessible label, falling back to position in the page only when nothing better exists. Selectors based on position are the ones worth a human eye before the script goes into CI.

Replaying a flow

From the Flows library, open a saved flow and replay it. DigiRecord opens the starting page and performs every recorded step against the live site so you can watch it happen. It is useful for checking a flow still works after a site changed, and for demonstrating a process without doing it by hand.

Recording your desktop

Not everything happens in a browser. Press Ctrl+Shift+D, or choose Capture a Desktop Walkthrough, then pick what to capture: an entire screen, a single window with nothing behind it, or a custom area you drag a rectangle around.

A small floating control bar appears with pause and stop, and stays on top of whatever you are doing.

Pause does not cut the video. It stops new steps being captured, but the screen recording keeps rolling underneath. If you step away, trim the result afterwards, or stop and start a fresh recording.

Finding your work again

The sidebar has everything. Flows holds every saved recording, to open, replay, rename or delete. Tutorials holds every generated guide, to view, edit, export or delete. Dashboard shows how much you have recorded and which sites most. Account is your plan, trial, usage and licence.

Your account, trial and licence

DigiRecord starts a 14 day trial the first time you launch it, with the full Pro feature set. No account, no email, no card. It is capped at 10 recordings, 3 exports and 5 tutorials.

When the trial ends, or a cap is reached, DigiRecord tells you which feature is affected and why, rather than quietly disabling a button. Your recordings are never deleted, and the Dashboard keeps working so you can still see your own data.

Activating a licence. Open Account, paste the key from your purchase email into the licence box, and press Activate. The key is case insensitive and the dashes are optional. A mistyped key is caught immediately, before the app contacts the server, because the key carries its own checksum.

Working offline. After activation DigiRecord works offline. It checks in about once a week and tolerates 30 days with no connection at all, so a plane, a hotel or a hostile firewall will not lock you out.

Moving to another computer. Open Account on the machine you are leaving and press Deactivate this computer. That frees the seat immediately and you can activate on the new one straight away. No support ticket needed.

Updates

DigiRecord checks for a new version shortly after launch, and whenever you choose Help → Check for Updates. When one is available it downloads quietly in the background and the Account page then offers Restart and install. Nothing ever installs on its own.

A licence includes updates for a period, shown on the Account page as Free updates until. After that date DigiRecord keeps working exactly as it is, forever. It simply stops offering newer versions, and renewing brings them back.

Where your work is stored

Everything is on your own computer, under %APPDATA%\digirecord\. Recordings and the tutorial index live in digirecord.db; screenshots, generated guides and exported scripts live in user_data\; your plan and licence state lives in account-state.json.

Back up that one folder and you have backed up all of your work. There is no cloud copy, which is the point, but it also means the backup is yours to make.

Keyboard shortcuts

When something goes wrong

Send us the log. Help → Open Logs Folder opens the folder containing main.log. Attach it to an email to support@screenpager.com and we can usually find the cause without a single follow up question. The log never contains your licence key, passwords or tokens; those are removed automatically before anything is written.

Getting help

Support: support@screenpager.com
Sales and licensing: sales@screenpager.com