Recording → guide
Turn a screen recording into a step-by-step guide.
Everything Loom charges for — free.
You recorded a 9-minute demo of how to provision a database. Now your new hire, your support team, your future self three months from now, and three other stakeholders all need to follow the same procedure. Sending them the video means each of them has to scrub 9 minutes to find the 30-second moment that matters to their question. Sending them a written guide means you spend 45 minutes writing it.
Pullsy generates the guide from the recording. You record once, you ship both — the video and a numbered, scannable step-by-step walkthrough with the recording embedded inline. Loom doesn't have this feature at any tier. Pullsy does, free.
Before vs after — the same walkthrough as a video, then as a guide.
Here\'s a concrete example. A 9-minute screen recording of provisioning a database, then the Pullsy-generated guide from the same recording.
The recording — 9 minutes, "click here, then type this, then click that"
- 0:00 — "OK, today I'm going to walk you through provisioning a new database."
- 0:23 — opens the Settings page, scrolls, points at a menu
- 0:58 — "OK so click Provision..."
- 1:47 — picks a region, "make sure you pick the closest region to your users"
- 3:22 — types in credentials, narrates "no, actually we don't need that field"
- 5:11 — clicks Confirm, waits for the deployment to finish
- 7:48 — verifies the health check, "OK so if this is green, you're good"
- 9:00 — closes with "let me know if you have questions"
The problem: Viewer has to scrub 9 minutes to find "what region do I pick?" or "which field did you skip?" Pause, rewind, pause. Three viewers, three different questions, all of them bouncing off the video.
The Pullsy-generated guide — numbered, scannable, video embedded
- Step 1: Open Settings → Databases → New Database
- Step 2: Click Provision (visible in the recording at 0:58)
- Step 3: Pick region eu-west-1 (or the region closest to your users — see 1:47)
- Step 4: Skip the "Optional Backup Tag" field (it's not required — see 3:22)
- Step 5: Click Confirm
- Step 6: Wait for the deployment indicator to turn green
- Step 7: Verify the health check on the Status tab (see 7:48)
- Need more context? Click any step to jump to that moment in the recording.
The benefit: Viewer scans the 7 numbered steps in 20 seconds. If a step is ambiguous, they click the embedded timestamp and hear the original narration. Same content, two ways to consume it.
When to ship the video, when to ship the guide, when to ship both.
| Situation | Video? | Guide? | Why |
|---|---|---|---|
| Async customer support ticket | Maybe | Yes — the customer wants to scan, not watch | A support ticket is read in 30 seconds. A video is watched (maybe) in 5 minutes. The guide gets the resolution faster; the video is the fallback for ambiguous steps. |
| Internal onboarding for a new hire | Yes | Yes — both | The new hire reads the guide to onboard (faster, indexed, searchable) and watches the video on day 30 when they want a refresher on a specific section. |
| Tutorial published on a blog or docs site | Yes | Yes — both | Most readers prefer text for the happy path; they watch the video for edge cases. Shipping both is the right move for SEO and for accessibility. |
| Quick bug-report walkthrough to an engineer | Yes | No — just the video | The engineer is going to watch the video to see the bug. The guide adds nothing here. Skip the export. |
| Sales follow-up with a prospect | Yes | No — just the video | A prospect wants to see you, hear your voice, and feel the personal touch. A written guide reads as a "we sent this to everyone." Video only. |
Recording-to-guide: Loom vs Pullsy.
| Feature | Loom | Pullsy |
|---|---|---|
| Auto-generate a step-by-step guide from a recording | No — Loom has no equivalent | Yes — free |
| Guide includes clickable timestamps back to the recording | N/A | Yes |
| Embed the recording inline within the guide | N/A | Yes |
| Edit the auto-generated steps | N/A | Yes — edit any step, add or remove |
| Export the guide as Markdown / HTML / PDF | N/A | Yes — export to Markdown and HTML, free |
| Cost to unlock this feature | Not available | Free |
Recording-to-guide — the headliner.
Pullsy converts a finished recording into a numbered, step-by-step written guide — essentially an auto-generated SOP. Each step pulls a short caption from the transcript and embeds the moment in the recording it came from. Loom has no equivalent at any tier.
Ask-this-video — so readers can ask back.
A guide plus a recording plus an Ask-this-video panel means readers can scan the guide, jump to the relevant moment in the video for ambiguous steps, and ask the recording a question if neither of those answered them. Loom has no chat-with-the-video feature at any tier.
Auto-summary + chapters, free.
The guide is one of three written artifacts Pullsy generates per recording. You also get an auto-summary and a chapter list — both free, both gated behind Loom Business + AI (~$20–24/user/mo) on Loom.
Frequently asked questions
Does it handle multi-step workflows with branches?
Pullsy generates one linear sequence of steps from the recording. If your workflow has branches ("if you're using SSO, do X; if you're not, do Y"), Pullsy will pick up both as separate steps in the order you narrated them. For complex branching procedures, you can edit the generated guide to add a conditional note — but Pullsy doesn't auto-detect branching structure.
What if the AI gets a step wrong?
Every generated step is editable. After the guide is generated, you click any step and rewrite the text. The video timestamp stays correct — only the written caption changes. Most teams generate, skim for accuracy, and edit the 10–20% of steps that need clarification.
What format does the guide export as?
The guide exports as Markdown (for pasting into Notion, GitHub, your docs site) and HTML (for embedding in a help-center article or internal wiki). Markdown is the default. Pro tier adds PDF export and a custom-domain share URL for the guide itself.
Does the guide include screenshots from the recording?
Pullsy captures a representative frame from each step and embeds it inline in the guide — readers see a small screenshot of what the step looks like at that moment in the recording. For text-heavy steps, the screenshot is optional and can be hidden.
Does this replace a help-desk tool or knowledge-base platform?
No — it generates the content for one. Pullsy produces the Markdown and HTML you paste into whatever you already use (Notion, Confluence, GitHub, your docs site, Zendesk). Pullsy doesn't store tickets or run a support inbox.
Is Pullsy affiliated with Loom?
No. Loom is a trademark of Atlassian. Pullsy is an independent product not affiliated with or endorsed by Loom. Plan details above are dated to July 2026 from Loom's public pricing pages.
Record once. Ship the video and the guide.
No install, no signup, free. One tab.
Loom is a trademark of Atlassian. Pullsy is not affiliated with or endorsed by Loom. Loom plan details reflect Loom's public pricing pages as of July 2026.