Profiles
A Profile is a named snapshot of the current site's cookies. Save the set you have now, then switch to another saved set in one click — no logging in and out, no hand-editing a dozen cookies each time you change scenario.
When to Use Profiles
- Test user states — logged-in, guest, admin, trial vs paid.
- Reproduce a bug that only happens for a particular cookie set.
- Demo flows — jump between prepared states while presenting.
- Reset quickly — snapshot a known-good set and return to it after a messy test.
Profiles change a whole set of cookies at once. To pin a single cookie against changes, use Freeze instead.
Saving a Profile
- Get the site's cookies into the state you want.
- Open the Profiles view and save the current cookies under a name — for
example
logged-in,guest, oradmin.
Switching Profiles
Select a saved profile to apply its cookie set to the site. Reload the page to let the app pick up the new state.
Export & Import
Profiles export and import as a file, so you can share a scenario with a teammate or move it between machines.
- Export a profile to a file.
- Import a profile from a file.
Imports are scoped to the current site. A profile captured on one site can't inject cookies into another, which prevents session-fixation-style mistakes.
Storage & Privacy
Because a profile has to restore cookie values, Cookie Lens keeps those values in local extension storage — on your device only, never transmitted. See the Privacy Policy.
See Also
- Editing Cookies — adjust cookies before saving a profile.
- Freezing Cookies — pin a single cookie instead of a set.
- Inspecting Cookies — build the state you want to save.