Guests, accounts and signing up

There is no login wall

Anywhere. A visitor who has never seen a sign-in screen can paste a URL and get a demo, and that is a rule the product is built around rather than a growth tactic.

Concretely: the account is created on the write, not on the page render. Opening the composer, the library or a share page creates nothing. Pressing the button that makes a demo is what mints an identity, and it does it silently.

What a guest is

A guest is a real account with no password and no email you gave us. It is stored on your browser as a cookie, and it owns your demos, your library and your saved sessions exactly as a signed-in account would.

There are no feature walls on a guest. Not on the editor, not on sharing, not on projects, not on recording behind a login. Cost is bounded by daily limits rather than by gates — see Daily limits and the in-flight cap.

What signing up adds

Three things, and the first is the important one:

1. Durability. Your work stops depending on one browser's cookie. Clear your cookies as a guest and the demos are still there, but nothing can prove they are yours.
2. A bigger daily allowance, and a bigger in-flight cap.
3. The ability to buy Pro, and to build a team — a subscription and a shared workspace both have to outlive a browser session, which is why neither is offered to a guest.

Sign-up is email and password, or Google.

Nothing you made as a guest is lost

Signing up with a new email keeps the same underlying account. Your demos, your library, your saved sessions, your projects and your share links all carry over — none of them is copied, moved or re-created, because the identity behind them does not change. It stops being a guest and starts being you. Everything that gates on guest-ness flips at once, in the same instant, including your daily allowance.

Arriving at an account that already exists moves them instead — continuing with Google or Apple, or signing in with an email and password you already had. That account may be one you have held for a year, so your demos and your projects move into its personal workspace and appear in its library, whether it is brand new or already has work in it; nothing of yours and nothing of that account's is replaced, and your daily allowance is whatever that account's plan gives it. Two things stay behind on the guest: anything you uploaded to your media library, and any saved session — both are stored under the identity that uploaded them, so moving the row would leave it pointing at somebody else's file. Sign up with a new email first if you have either and you want them.

Signing in

The sign-in and sign-up forms are server forms. They submit and establish the session on the server, which means two things: they work with JavaScript disabled, and they are safe to submit the instant the page arrives rather than after it has finished loading.

Both of those were once not true, and one of the failures put a plaintext password in a URL for anybody who typed fast enough. They are stated here because "the form works before the page has hydrated" is exactly the kind of guarantee nobody thinks to check.

The one thing a guest is refused

Deleting the account itself. A guest has no password, so the freshness check that protects an account deletion is the only one that could run, and a guest cannot re-authenticate to pass it — "sign in again" would be a dead end.

What a guest can do instead is Delete everything, which removes every video and every asset they hold. See Deleting a video, a library or an account.