Skip to main content
Stop logging in from scratch on every run. TinyProfiles let TinyFish save browser state — cookies, local storage, and session storage — and reuse it later. Recurring automations can start where a real returning user would: already signed in, with the right workspace, preferences, and site context loaded.
TinyProfiles are not Browser Profiles. Browser Profiles choose the runtime mode with browser_profile: "lite" | "stealth". TinyProfiles save session state across runs.

Use the API

Create and run with TinyProfiles programmatically

Vault Credentials

Add stale-session repair

The flow

1. Set up once

Open a setup browser, sign in, and save the session.

2. Run many times

Reuse saved state so recurring runs start authenticated.

3. Repair when stale

Add Vault so TinyFish can log back in if the session expires.

Set up a TinyProfile

  1. Go to TinyProfiles in the TinyFish dashboard.
  2. Click Create Profile.
  3. Name the profile.
  4. Optional: mark it as the default profile.
  5. Optional: choose a proxy location for the profile.
  6. Click Create and set up.
  7. Sign in to the target site in the setup browser.
  8. Save the setup session.
Use one TinyProfile per account or environment, such as Salesforce Production and Salesforce Sandbox.

Use a TinyProfile

  1. Open the Playground.
  2. Click the profile icon in the toolbar.
  3. Turn on Use TinyProfile.
  4. Choose a profile, or use your default profile.
  5. Run the automation.
If no profile exists, click Go to TinyProfiles to create one first.

Manage TinyProfiles

On the TinyProfiles page, you can:
  • Rename TinyProfiles
  • Set a default TinyProfile
  • Copy a profile ID
  • View saved domains
  • Set or clear a profile proxy location
  • Upload cookies manually
  • Delete individual domains
  • Delete TinyProfiles
You cannot delete your only active profile. Create another profile first.

TinyProfiles + Vault

The best authenticated setup is TinyProfiles plus Vault Credentials.

TinyProfiles

Keep persistent logged-in browser state across runs.

Vault

Provide matching credentials when a login form appears.

Together

Repair stale sessions instead of logging in cold every run.
Use this pairing for authenticated workflows where sessions expire over time. The TinyProfile starts the run with saved state. If that state has gone stale and a matching Vault credential is available, TinyFish can sign in again and refresh the profile state for future runs.
1

Start with saved state

TinyFish opens the site with the cookies and storage saved in the TinyProfile.
2

Detect stale login

If the site asks for login again, the agent proceeds through the normal login flow.
3

Repair with Vault

When use_vault: true is set and a matching credential exists, TinyFish can use it to restore the session and keep future profile runs healthy.
Start with TinyProfiles for persistence, then add Vault for stale-session repair. This is usually more reliable than asking the agent to log in from scratch on every run.

When to use TinyProfiles

Proxies and stealth mode

TinyProfiles answer “what state should this run start with?” Proxies and Browser Profiles answer “how should the browser connect and behave?” Choose a profile proxy location when a logged-in session should consistently come from the same country. Leave it blank when location should be decided per run with Proxies. Use Browser Profiles when you need lite or stealth runtime mode.

Limits and expectations

Next steps

TinyProfiles API

Manage profiles programmatically

Vault Credentials

Add stale-session repair

Browser Profiles

Choose lite or stealth runtime mode