---
title: "Record an article or changelog with the Chrome Recorder"
description: "Do a task once in Chrome and get a drafted step-by-step help article or changelog entry, ready to review and publish."
url: https://help.gleap.ai/en/articles/267-record-an-article-or-changelog-with-the-chrome-recorder
collection: "Help center"
updated: 2026-10-17
language: en
---

# Record an article or changelog with the Chrome Recorder

Do a task once in Chrome and get a drafted step-by-step help article or changelog entry, ready to review and publish.

Writing a step-by-step guide usually means doing the task, then describing it from memory, and the memory is where mistakes creep in. The Chrome Recorder closes that gap. It watches the tab while you do the task once and drafts the write-up from what actually happened, screenshots included.

It makes two kinds of draft from the same recording: a help article or a changelog entry. Turning a recording into a draft uses AI credits.

### Install and connect

1.  Install the [Gleap Recorder from the Chrome Web Store](https://chromewebstore.google.com/detail/gleap-recorder/pjknnhpaknnifjdioiabjlmpjogheabh). The Gleap icon appears in your toolbar.
    
2.  Click the icon and sign in with your Gleap account.
    
3.  If you work in several projects, pick the right one in the dropdown at the top of the recorder. Check it before every recording, so the draft doesn't land in the wrong place.
    

### Record

1.  Choose what you're recording: a help article (a step-by-step guide) or a changelog (a release note). This decides the shape of the draft.
    
2.  Choose how detailed it should be: brief for a short workflow with only the key steps, standard for most things, detailed when the guide needs extra context and tips.
    
3.  Optionally pick a microphone and narrate as you go. If no microphone is listed, allow microphone access first.
    
4.  Start recording, do the task once, and stop.
    

Narration is optional, since the draft can be built from your clicks alone. But it's what turns a list of steps into an explanation: it captures why you did something, which no amount of watching can work out.

Do the task the way a customer would, not the way you would. Experts skip steps without noticing, such as a keyboard shortcut or starting from a page nobody else has bookmarked, and those gaps end up as missing steps. Start where a customer starts, move deliberately, and avoid detours into anything you don't want documented.

> **Warning:** You're recording your screen with real data on it. Use a test account, or check what's visible. Customer names, email addresses and internal notes end up in the recording, and screenshots from it can carry them into a published article.

### Find and review the draft

-   A help article lands as a draft in a collection called **Recordings** in your help center. Gleap creates the collection the first time. While it's still being written, the collection shows the recording's progress.
    
-   A changelog lands as a draft changelog in **News**.
    

What arrives is a draft, and it should be treated as one. It's accurate about what you did, but it knows nothing about why the reader is there, what could go wrong, or what to do when it does.

1.  Retitle it as the task or question a customer has.
    
2.  Add the one prerequisite the recording assumed.
    
3.  Say what a successful result looks like.
    
4.  Move the article to the collection where it belongs, then publish it. A draft helps nobody and is invisible to your AI.
    

### Related

-   [Write articles your AI can use](https://help.gleap.ai/en/articles/259-write-articles-your-ai-can-use.md)
    
-   [Publish news and changelogs](https://help.gleap.ai/en/articles/326-publish-news-and-changelogs.md)
    
-   [Publish, brand and protect your help center](https://help.gleap.ai/en/articles/266-publish-brand-and-protect-your-help-center.md)
