# Recording

## Record

1. Open the web app you want to change, then the Skins side panel's **Record** tab.
2. Under **Project**, choose **New project** and name it, or **Existing** and pick one. A project
   holds one skin: record into the same project to keep working on the same change.
3. Press record and use the page. Page loads and in-page navigation are part of the same
   recording. While it runs, Chrome shows that Skins is debugging the tab: that's how it records the
   page's requests.
4. Press stop, then **Keep** to save the recording to the project, or **Discard**.
5. **Open in Studio** to shape the change ([Editing and publishing](/docs/editing/)).

## What a recording keeps

Only what happens between record and stop, in the tab you record:

- **How the page looked and changed:** its content, text and layout, as a replayable sequence, and
  its images, fonts and stylesheets, so the replay looks right. The page's own scripts aren't kept.
- **What you did:** clicks, scrolling and typing. What you type into fields is recorded, except in
  password fields.
- **The page's requests:** what the page asked its server and what came back, with request and
  response bodies for its API calls. Cookie, authorization and CSRF-token headers are replaced with
  `[redacted]`, and credentials are stripped from addresses. Everything else, bodies included, is
  kept as recorded.

Content inside embedded frames from other sites, and canvas drawings, isn't recorded. The files,
field by field: [Recording format](/docs/recording-format/). Where recordings are kept, and who can
read them: [Privacy and security](/docs/privacy/).