For support and docs teams
Show people where to click.
Record the answer once in Chrome. Embed it as a walkthrough in your help article, publish it as a written guide with screenshots, and fix it in the editor when the screen changes.
Support teams and technical writers
The job today.
-
Screenshots go stale
The product ships a change and twenty articles now show a button that moved. Retaking, cropping and annotating screenshots eats the week.
-
Customers still ask where to click
The article says “Go to Settings, then Billing”, and the ticket arrives anyway because the reader can’t find Settings.
-
Customer data in every capture
The clearest examples come from real accounts, so every screenshot needs names and emails blurred by hand before it goes public.
With AtriumKit
Put a walkthrough in the article
Embed a guided demo in any help center or docs page that accepts an iframe. Readers click through the real screens, and each step zooms in on where to look.
- Branching sends readers down the path that matches their setup
- AI translations into 15 languages on Pro and Team, in the reader’s browser language
- Step analytics show where readers give up (Pro and Team)
The written guide comes with it
Every published demo is also a step-by-step guide with a picture per step and the click highlighted. Copy it into your docs tool, or link to the hosted guide page.
- Copy as rich text or Markdown, download a
.mdfile, or print it to PDF - Give a step its own guide text, or hide it from the guide
- Write guide copy drafts the text with AI in your instructional voice
- Your support team finds the guides in the internal knowledge base (Pro and Team)
Keep customer data out of it
While you record, the extension blurs emails, phone numbers and names in your browser, before anything is uploaded. Blur more as you go, or later in the editor.
- Auto-blur emails and names is on by default
- Blur area on the recording bar, and the Blur tool in the editor
- Blurred pixels never appear in the published demo or guide
Fix it when the UI changes
A renamed button or a new label doesn’t need a new recording. Change the text in the editor, point a step at another screen, or record only the new screens. When a whole flow changes, record it again.
- Edit text on a screen, or Find & replace across every HTML screen
- Swap a step’s screen for another screen in the same demo
- + Capture more screens records new screens into a clickable demo
- Publish once and the walkthrough, the embed and the guide all update
Where to start.
-
Guided demos
Step-by-step walkthroughs with tooltips, zoom and branching paths.
-
Step-by-step guides
Every published demo is also a written guide with screenshots, ready for your docs.
-
Editor
Change page text, blur data, hide banners and swap images after you record. Every version is saved.
-
Chrome recorder
Click through your product once in Chrome. Every click becomes a step.
-
AI writing and translation
Draft every tooltip from your screens, rewrite a step in one click and translate the demo into 15 languages.
-
Knowledge base
Every demo as a searchable how-to, plus what AI should know about your product.
Playbooks
All playbooksFAQ
Questions, answered.
Do I have to re-record when the UI changes?
Not for small changes. Use Edit text on a screen, Find & replace across HTML screens, or switch a step to another screen in the demo. In a clickable demo, + Capture more screens adds new screens. If a whole flow changed, record it again. See capture more screens.
Can I export the guide?
Yes, on every plan. Copy it as rich text or Markdown into Notion, Google Docs or Confluence, download a .md file, or use Print / PDF to save it from your browser.
Is customer data uploaded before it’s blurred?
Not when you blur while recording. Auto-blur emails and names and Blur area work in your browser, so the original pixels and text never leave it. Blur you add later in the editor is baked into the published image.
Is the text inside the screens translated?
No. AI translation (Pro and Team) covers tooltips, cards, buttons and the written guide. Text inside the captured screens stays as you recorded it.