Source: https://polysh.io/product/guides/ > **Reading this as an agent?** This is the Markdown copy of a polysh.io page, written for people and agents alike. To learn what Polysh can do for you and your user, start at https://polysh.io/agents/, and use https://polysh.io/llms.txt for an index of every page. Agent features are in early access, so there's nothing to install yet; your user can join the waitlist at https://app.polysh.io/waitlist. Step-by-step guides # Turn a screen recording into a step-by-step guide Polysh writes numbered steps from your recording, each with a checked screenshot of the screen you acted on, and blurs private details. [Request early access](https://app.polysh.io/waitlist)[See an example guide](https://polysh.io/examples/) Make a guide, a video, or both in one export. ## Written for doing, not watching A demo is for watching. A guide is for following along with the product open. ### Summary and audience What the task is and who it's for. ### What you'll need Anything to have ready first, such as access to Reports. ### Numbered steps, grouped by task What to do, what you should see next, and an optional tip. ### Notes and comparisons Side remarks become notes, and compared options sit side by side. **Step 2: Choose Monthly usage.** Under **Report type**, select **Monthly usage**. You should see: a preview of last month's usage by team. Tip: Save the report to reuse the same filters next month. ## Screenshots checked against each step A missing screenshot is better than a wrong one. 1. 1### Plan Polysh splits the walkthrough into steps and links each to the click that performs it. 2. 2### Capture It takes candidate frames around each click, never from parts you trimmed. 3. 3### Check A vision model keeps a frame only if it clearly shows that step. 4. 4### Leave it out if unsure If none passes, pick a candidate yourself or keep the step as text. The check also reads on-screen labels. If you said "Reports tab" but the button says **Insights**, the guide says **Insights**. ## Private details stay blurred ### Flagged automatically The check looks for names, email addresses, and account details in every screenshot. ### Blurred in the editor Until someone on your team reveals it. ### Hidden from guests People outside your workspace never see it on a shared page or in its PDF. ### Your call in your own PDF Polysh asks whether to include flagged screenshots. ## Edit it like a document ### Text and order Edit the title, summary, and any step. Drag to reorder or delete. ### Swap the screenshot Pick another candidate frame, or remove it. ### Safe for teams Every edit is saved as a new version. If someone else changed the guide first, Polysh loads theirs before you overwrite it. ### Knows when it's out of date If the script changes, the guide flags it and offers to remake it. ## A guide in each language Each language's guide is written from that language's reviewed script, so the guide and the video say the same thing. ### Pick languages at export Tick the languages you want and choose guides, videos, or both. ### Readable in every script Hindi, Tamil, Japanese, and the rest render in their own script, on the page and in the PDF. [See all 16 languages](https://polysh.io/product/translation/#languages) ## Share a page or save a PDF Send a web page with its own link, or save a PDF with selectable text. The link stays the same when you remake the guide. ### Who can open it Invited people confirm with an emailed code, or open it to anyone with the link. ### Expiry, downloads, activity Set an end date, turn off PDF downloads, and see who viewed or downloaded. [All sharing controls](https://polysh.io/features/#sharing) ## Step-by-step guide or video? Most teams make both from one recording. | A guide is better when… | A video is better when… | | ----------------------------------------- | -------------------------------------------------- | | People follow along with the product open | People want to see the whole flow first | | They need to scan back to one step | The order and pace matter, such as a launch demo | | It lives in a help article or SOP | It plays in onboarding, release notes, or a course | | Some readers can't play audio | Seeing the motion explains it faster than words | [Use cases for teams](https://polysh.io/use-cases/) ## Questions about guides **Do I need to record anything extra for a guide?** No. Tick "Step-by-step guides" when you export. **Can I make a guide without a video?** Yes. Untick videos at export and you use no video credits. **What happens to my edits if I remake the guide?** They're replaced for that language, so Polysh asks you to confirm first. **Can people outside my company edit a guide?** Yes, as editors on the share link. They can edit text, reorder steps, and swap screenshots, but not remake or delete the guide. **Can I export the guide to my help center?** Not directly yet. Share it as a page or save a PDF, and [tell us](https://polysh.io/contact/) which help center you use. ## Related free tools ### Add Numbered Steps to Screenshot Drop numbered step badges that match the order of your written instructions. [Open tool](https://polysh.io/tools/add-numbered-steps-to-screenshot/) ### Screenshot Annotation Tool Mark up a screenshot with every kind of annotation in a single editor. [Open tool](https://polysh.io/tools/screenshot-annotation-tool/) ### Screenshot Redaction Tool Cover secrets in a screenshot with solid boxes that leave nothing to read. [Open tool](https://polysh.io/tools/screenshot-redaction-tool/) ### Markdown to HTML Get indented HTML source from your Markdown, ready to paste into a CMS or save. [Open tool](https://polysh.io/tools/markdown-to-html/) ## Get the guide with your next video Make both from your next recording. Founding teams keep their rate. [Request early access](https://app.polysh.io/waitlist)[Already invited? Sign in](https://app.polysh.io/sign-in)