Drıftstack docs
Docs

Restoring a snapshot counts as a profile (limit)

You might be here because: “keeps N saved profiles, and this account already has N” · “can’t restore a snapshot” · “429 tier-limit on restore” · “do snapshots count against my profile limit” · “Profile name already exists in this account” · “the restored profile has no cookies” · “what is a profile snapshot” · “how many snapshots can I keep” · “A usage limit was reached. Wait a moment or review your plan, then try again”

Short answer

A snapshot is a frozen record of a profile’s device, name and description, and keeping snapshots costs nothing against your profile limit — restoring one creates a new profile, which does count. If you are at your plan’s number, delete a profile you no longer need (a profile in the Trash does not count), then restore.

Check first

  • Count your live profiles: the check counts those only, and profiles in the Trash do not count.
  • Does the name you gave the restored profile already exist? That is refused separately, with “Profile name … already exists in this account.”.
  • Expecting cookies or logins back? A snapshot holds metadata only; the restored profile starts with empty browser state.

Likely causes and fixes

  1. You are at the limit. Restore is refused with HTTP 429 tier-limit, detail “Your plan (…) keeps N saved profiles, and this account already has N. Delete a profile to free a slot, or choose a plan with more profiles.” — the same gate as creating a profile. The desktop app shows the generic “A usage limit was reached. Wait a moment or review your plan, then try again.”. Fix: delete a profile you are done with, or move to a higher plan — self-serve for Starter, Pro and Team from the dashboard → Billing → Choose a plan; Scale and Enterprise are arranged with a person. The numbers per plan are on the profile-limit page.

  2. Two restores or creates at the same moment. The count is re-checked under a lock, so the second one can be refused even if the list looked to have room. Fix: free a slot, then retry.

  3. The name is taken (409). Restore creates a fresh profile, so its name must be unused in the account. Fix: choose another name.

  4. The snapshot’s device is not on your current plan. A restore makes a profile on the snapshot’s device, and your plan today must include that device — the snapshot may be older than a downgrade. Fix: see which devices your plan can choose.

  5. Is this the same as restoring from the Trash? No. Restoring a snapshot creates a new profile and does not use one of your plan’s restores from the Trash.

  6. How many snapshots can I keep? There is no per-account snapshot quota today.

If it still fails

If you freed a slot and the restore is still refused, press Talk to a person in this chat (or open Help) and include your plan, the number of profiles shown, the snapshot id and the exact sentence.