100% on-device — screenshots never leave your computer

How to Create an SOP from Screenshots
Without Uploading Anything to the Cloud

A practical guide to building polished, annotated SOPs directly from your browser — with no account, no subscription, and no data leaving your device.

Add to Chrome — it's free

What is an SOP and why screenshots make it 10x faster to write

A Standard Operating Procedure (SOP) is a documented sequence of steps that describes exactly how to complete a repeatable task. Done well, it lets any team member — on their first day or fifth year — perform a process consistently without supervision.

The problem with writing SOPs the traditional way: you have to remember what you did, reconstruct it from memory, and describe each step in enough detail that a stranger could follow it. That is slow, error-prone, and never quite matches what actually happens on screen.

Screenshots change the equation entirely. Instead of writing "click the dropdown in the top-right corner," you show it. A screenshot with a numbered annotation eliminates ambiguity. A reader glances at the image for two seconds and knows exactly what to do — no paragraph of prose required.

A well-established principle in instructional design is that people follow procedural tasks more accurately with annotated visuals than with text descriptions alone. Many SOP writers find that capturing screenshots during a task significantly reduces documentation time compared to reconstructing steps from memory after the fact — the capture workflow eliminates the reconstruction step entirely.

The challenge is the workflow. Most teams either screenshot manually (messy, inconsistent numbering), use cloud-based guide tools (privacy concerns, subscription costs), or skip SOPs entirely and rely on Slack threads and institutional memory. StepSnap closes that gap: it captures a screenshot at every click automatically, numbers each step, and assembles the guide — all inside your browser, with nothing transmitted to a server.

The old way: manual screenshots and a Google Doc (and why it breaks down)

The most common SOP workflow looks like this:

  1. 1Open a Google Doc alongside your browser window.
  2. 2Do the task once, pausing every few clicks to hit Print Screen and paste into the Doc.
  3. 3Go back and add step numbers, labels, and arrows — one image at a time, in a word processor not designed for this.
  4. 4Realize the screenshots are different sizes, the numbering is off, step 7 is missing, and the doc is already 40 MB.
  5. 5Spend 45 minutes reformatting. Repeat every time the UI changes.

The fundamental problem is that manual capture breaks your flow. Every time you stop to take a screenshot you interrupt the task, which means you frequently miss steps, capture the wrong moment, or get distracted and forget where you were.

Paste-into-Google-Docs also has a silent privacy issue: your screenshots may contain customer names, internal URLs, API keys in address bars, or sensitive form fields. Pasting them into a cloud document transmits that data to Google's servers — something most teams never think about until a compliance review flags it.

Cloud guide tools like Scribe and Tango automate the capture part, but they move the privacy problem upstream: Scribe and Tango both require a cloud account — every guide you create is stored on their servers, not on your device. For teams handling client data, internal systems, or anything regulated, this is a blocker, not a feature.

The right solution captures automatically (no pausing, no missed steps) and keeps every screenshot local (no cloud storage, no account required).

The right SOP structure: purpose, scope, steps with annotated screenshots

A well-structured SOP has four parts. You do not need a template tool or a Word macro — a simple, consistent pattern is enough:

1. Purpose One sentence: what does this procedure accomplish? Example: "This SOP describes how to create a new client account in the CRM." Write this last — it is easier once you have captured the steps.
2. Scope Who performs this task, when, and in what system? Include the software version or URL if the UI changes between versions. Example: "Performed by: Account Managers. System: CRM v4.2 (app.crm.example.com)."
3. Step-by-step with annotated screenshots Each step = one action + one screenshot with a numbered marker on the element clicked or field filled. Use plain language: "Click Save" not "Select the persistence action."
4. Notes and edge cases A short section at the end for "what if." Example: "If the Save button is greyed out, the required fields marked in red are incomplete." This is where experienced knowledge lives.

Keep each step to a single action. If a step reads "Click Settings and then select Billing and enter your card number," split it into three steps. Single-action steps with screenshots are impossible to misinterpret.

Annotate the screenshot immediately — a number badge or an arrow pointing at the relevant element saves a reader 10–15 seconds per step compared to scanning an unannotated image. StepSnap places the number chip automatically at the click point.

Step-by-step: record a live workflow with StepSnap (no setup, no account)

Unlike cloud guide tools, StepSnap requires no account creation, no email verification, and no API key. Install the Chrome extension and it is ready immediately. Here is the full workflow:

  1. 1Install StepSnap from the Chrome Web Store. No sign-up screen, no onboarding wizard — the extension icon appears in your toolbar immediately.
  2. 2Navigate to the starting point of the workflow you want to document. For example, the login page of your CRM, your company's expense portal, or a web-based admin dashboard.
  3. 3Click the StepSnap icon and press Capture (or use the keyboard shortcut Alt+R). A subtle indicator shows recording is active.
  4. 4Perform the task normally. Every click is captured as a screenshot with a numbered marker at the click point. Do not pause — just do the task at your normal speed.
  5. 5Press Stop when the task is complete. StepSnap assembles the captured screenshots into a numbered guide instantly, entirely in your browser.
  6. 6Review the guide. Edit step titles, delete any accidental or redundant clicks, reorder steps if needed. No account, no sync — the guide lives in your browser's local storage.
  7. 7Blur sensitive regions before exporting (see the section below on sensitive data).
  8. 8Export or share. Copy the guide as HTML to paste into Notion or Confluence, download a PDF, or export Markdown for a GitHub wiki.
Privacy note: At no point in this workflow does any screenshot leave your browser. There is no upload step, no cloud sync, and no server processing. All capture and assembly happens locally.

Total time from install to a finished, shareable SOP for a typical 10-step workflow: under five minutes, including review.

Annotating and numbering your screenshot steps automatically

Annotation is where most manual SOP workflows fall apart. Adding arrows and number badges in Google Slides or PowerPoint is tedious, inconsistent, and breaks every time someone edits the document. StepSnap handles annotation at capture time so you never have to open an image editor.

Auto-numbered markers Each click point gets a numbered chip placed directly on the screenshot at the pixel location of the click. Steps are automatically renumbered if you reorder or delete them.
Editable step titles The default title is the text of the element clicked (button label, link text). You can rename any step — useful when the UI label is technical jargon and your SOP audience is non-technical.
One-drag blur regions Draw a rectangle over any area of a screenshot to apply pixelation. Works on any content: a customer name in a sidebar, an internal URL in the address bar, a partially visible password.
Delete redundant steps Accidental clicks, hover states, and intermediate loading screens are easy to remove. The remaining steps renumber automatically.

The result is a guide where every screenshot is the same width, every annotation uses the same visual style, and every step number is sequential — without you having to do any of that formatting manually.

If you need to add context between steps — a warning, a note about a common mistake — you can insert a text-only step between any two screenshot steps. This keeps the guide self-contained without breaking the visual flow.

How to handle sensitive data on-screen (PII, passwords, internal URLs)

Sensitive data appears in SOP screenshots constantly. A CRM workflow will show customer names. An HR onboarding guide will show employee records. An admin portal SOP will show internal URLs that reveal infrastructure details. Handling this badly is not just an embarrassment — it is a compliance risk.

The first and most important protection StepSnap provides is architectural: because screenshots are never uploaded to any server, there is no third-party handling of your sensitive captures at any point. Compare this to cloud guide tools, where advanced features such as PII/PHI redaction are locked behind custom-priced Enterprise tiers — meaning most teams on standard plans are uploading unredacted screenshots to a vendor's infrastructure.

Beyond architecture, StepSnap gives you three practical tools:

  1. 1One-drag pixelation. After capture, draw a selection rectangle over any region of any screenshot. The selected area is immediately pixelated. This is the fastest way to redact a specific field without editing the whole image.
  2. 2Delete the step entirely. If a step's screenshot captures something that should not appear in any form — an error message with internal stack trace, a screen with multiple customers' data — delete the step and add a text-only step in its place describing the action.
  3. 3Use a sanitized account for capture. For SOPs involving customer-facing systems, create a demo account with dummy data before recording. This eliminates the problem at the source.

For regulated industries (healthcare, finance, legal), run through the privacy checklist in the section below before sharing any SOP externally. The checklist takes under two minutes and catches the most common categories of accidental disclosure.

Address bar awareness: Internal hostnames, staging URLs, and subdomains often appear in address bars and can reveal infrastructure details. Review address bar content in every screenshot — blur it if the URL is not intended for the SOP audience.

Exporting your SOP to PDF, Word, or shareable link

Once your guide is reviewed and annotated, StepSnap offers four export paths designed to fit existing documentation workflows:

PDF export Generates a clean, print-ready PDF with one step per section, screenshot embedded at full width, and the step title above each image. Share via email or upload to a shared drive. No cloud service required to generate.
HTML export A self-contained HTML file you can paste into Notion, Confluence, or any wiki that accepts HTML blocks. Paste once — screenshots are embedded as base64, no external hosting needed.
Markdown export Numbered Markdown list with screenshot images encoded inline. Paste directly into a GitHub README, a GitLab wiki, or a Markdown-based knowledge base like Docusaurus or Outline.
Copy to clipboard Copies a rich-text version directly to your clipboard. Paste into Google Docs or Microsoft Word and the steps arrive pre-formatted with images inline.

Note: export to PDF, HTML, and Markdown is available on the free tier with a small "Made with StepSnap" badge. The Pro plan ($29 one-time, up to 3 devices) removes the badge and unlocks clean, unbranded exports suitable for client-facing documentation.

Unlike cloud guide tools that gate export formats behind paid plans — Scribe's free Basic tier supports unlimited guide creation for web apps, but export (PDF/HTML/Markdown) requires a paid plan — StepSnap's free tier includes all export formats, just with a branding badge.

SOP templates for common use cases: onboarding, CS handoff, client reporting

The fastest way to start a new SOP is to follow a consistent structure for each use case. Here are ready-to-use outlines for the most common scenarios. Capture the steps with StepSnap and drop them into the structure below.

Employee / user onboarding SOP
  • Purpose: first-day system access setup
  • Scope: HR or IT, performed once per new hire
  • Steps: create account, set password, assign role, confirm email
  • Notes: common errors and who to contact
Customer success handoff SOP
  • Purpose: transfer client from Sales to CS in CRM
  • Scope: Account Executive at deal close
  • Steps: update stage, assign CS owner, log kickoff notes, send intro email template
  • Notes: what to verify before marking complete
Client reporting SOP
  • Purpose: generate and deliver monthly performance report
  • Scope: Account Manager, performed on the 1st of each month
  • Steps: pull data export, apply filters, add commentary, export PDF, send via email
  • Notes: data lag warnings, escalation path if data is missing
Software / feature release SOP
  • Purpose: deploy and verify a production release
  • Scope: Engineering lead, performed per release cycle
  • Steps: merge branch, trigger pipeline, verify staging, approve production, monitor error dashboard
  • Notes: rollback procedure
Finance / accounts payable SOP
  • Purpose: process and approve vendor invoices
  • Scope: Finance team, weekly
  • Steps: open invoice queue, match PO, route for approval, mark paid, file receipt
  • Notes: approval thresholds and exception handling
IT access request SOP
  • Purpose: grant and document software access for new or changing roles
  • Scope: IT department, triggered by HR ticket
  • Steps: verify ticket, provision access in IdP, assign to group, confirm with requester, close ticket
  • Notes: required approvals by system sensitivity level

Each of these can be captured with StepSnap in a single session. For SOPs with branches (different steps depending on user role or system state), capture each path as a separate guide and link them from a parent "overview" document.

Privacy and compliance checklist before sharing your SOP

Run through this checklist before sharing any SOP externally or storing it in a shared drive accessible to large groups. It takes under two minutes and catches the most common categories of accidental disclosure.

Frequently asked questions about creating SOPs from screenshots

Does StepSnap upload my screenshots to a server?
No. All capture, annotation, and export processing happens entirely in your browser. Screenshots are stored in your browser's local storage and are never transmitted to any server. There is no account, no cloud sync, and no server-side component.
How is StepSnap different from Scribe or Tango?
Scribe and Tango both require a cloud account — every guide you create is stored on their servers, not on your device. Both tools also use a per-seat subscription model, so costs scale with your team size. StepSnap is 100% on-device and is sold as a one-time purchase with no per-seat fee. If data privacy or budget predictability matters to your team, those are the relevant differences.
Can I use StepSnap to document desktop apps like Excel or Photoshop?
StepSnap is a Chrome extension and captures browser-based workflows only. For documenting desktop applications (Excel, Photoshop, Figma desktop, etc.), you would need a separate screen-capture tool. Note that desktop app capture is also locked behind a paid plan on both Scribe and Tango.
What export formats does StepSnap support?
PDF, HTML, and Markdown — all available on the free tier with a StepSnap badge. The Pro plan removes the badge for clean, client-ready exports. HTML export is self-contained (screenshots embedded as base64), so you can paste it into Notion or Confluence without hosting images separately.
Is there a free plan?
Yes. The free plan includes unlimited capturing, all export formats, blur/annotation tools, and no time limit — with a small "Made with StepSnap" badge on screenshots. The Pro plan ($29 one-time, up to 3 devices) removes the badge and works offline forever.
How do I blur sensitive information in my screenshots?
After capture, click any screenshot in the editor and drag to draw a selection rectangle over the region you want to redact. The selected area is immediately pixelated. You can apply multiple blur regions to a single screenshot and they persist through all export formats.
Can I share a StepSnap guide with someone who does not have the extension?
Yes. Export as PDF or HTML and share the file directly — the recipient needs no account, no extension, and no login. The exported file is fully self-contained.
What happens to my guides if I uninstall the extension?
Guides are stored in your browser's local storage. Uninstalling the extension will remove them. Export any guides you want to keep before uninstalling. This is another reason to export to PDF or HTML as a matter of routine once a guide is finalized.
Can I add text-only steps between screenshot steps?
Yes. You can insert a text-only step anywhere in the guide — useful for notes, warnings, or steps that do not involve a visible UI change (for example, "Wait for the import to complete — this takes about 30 seconds").
Is StepSnap suitable for compliance-sensitive industries?
The on-device architecture makes it significantly more suitable than cloud-based guide tools for regulated industries. Because no screenshots are transmitted to a third party, there is no vendor data processing agreement required for the capture step. Always consult your compliance team for specific regulatory requirements — but the baseline privacy posture is strong.

Start your first SOP in five minutes

Free plan, no account required, screenshots never leave your browser. Add to Chrome and record your next workflow.

Add to Chrome — it's free