Automatic blur
Eleven detectors — passwords, card numbers, API keys, government IDs and more. Turn on the ones that matter to you.
Blur passwords and personal data, and point readers at exactly what matters — built into the tool that captures your guides.
There's always a password on screen, or an account number, or a button nobody will find without an arrow pointing at it.
So you export the image, open something else to edit it, save it, and put it back. For every single screenshot.
Point readers at the right button with an arrow or a callout. Cover a password with one click, or let the detectors find it for you. Change any screenshot in any guide later without recording it again.
Eleven detectors — passwords, card numbers, API keys, government IDs and more. Turn on the ones that matter to you.
Arrows, callouts, highlights, boxes, and blur regions, on any step of any guide.
Autoblur covers a field before the screenshot is taken, so what it was hiding is never in the image at all.
Switch on the detectors you need. Passwords are on by default, and a CSS selector covers anything specific to your tools.
Matching fields are covered as you go. Click anything else you want hidden and it's covered too.
Add arrows, callouts, and highlights in the editor, then publish, link, or export the guide.
Make your first guide in a couple of minutes. No credit card, no setup, nothing to learn.
| The old way | With Stepily | |
|---|---|---|
| Hiding a password | Export, open an image editor, blur, save, re-import | Covered before the screenshot exists |
| Adding an arrow | A separate screenshot tool | Click, drag, place |
| Highlighting an area | Manual shapes in a design tool | Built-in highlight and box tools |
| Finding what to redact | Hope you didn't miss anything | Eleven detectors check every step |
| Fixing it afterwards | Re-record the whole guide | Edit any screenshot, any time |
| Tools involved | Your recorder, plus an editor | One tool, start to finish |
See how Stepily fits the work your team already does.
Onboarding, records, payroll, and audits.
See howFewer tickets, faster fixes, clear runbooks.
See howRepeatable SOPs across every location.
See howPatient intake, clinical workflows, and compliance documented.
See howClient onboarding, compliance, and loan processing documented.
See howPasswords, card numbers, email addresses, names, addresses, usernames, government IDs, phone numbers, API keys, financial figures, and one-time codes. Each is a separate switch, so you decide what gets hidden.
No. Each category is a purpose-built detector looking at the page, which is why it behaves the same way every run rather than guessing differently each time. You can also give it a CSS selector for anything specific to your own tools.
Not when autoblur catches it. The blur is applied in the page before the screenshot is taken, so the field is already covered in the only image that ever leaves your browser. Blur you add later in the editor is applied to a screenshot that has already been uploaded.
Yes. While recording, click any element on the page to cover it, and add blur regions to any screenshot afterwards in the editor.
Arrows, lines, text callouts, highlights, boxes, ellipses, and blur regions, plus a marker for the element that was clicked.
Yes. Open the step, change the annotations, and save. There's no need to record the guide again.
No, but the screenshots will already contain whatever was on screen. Add blur regions in the editor to cover it, or re-record that step if it shouldn't have been captured at all.
Yes, on every Stepily account.
Create a free account and turn on the detectors your team needs.
Stepily records what you do and writes the step-by-step guide for you.
Try Stepily free