Accounts and cloud sync
GTFS·X is usable without an account — you can edit, validate, and export a feed without ever signing in. Accounts add cloud sync across devices, hosted publishing, and per-organization features. This page covers what changes when you sign in, including the question new users ask most: "where does my work actually live?"
Anonymous editing
If you've never signed in, you're editing as an anonymous user. Your in-progress work lives in your browser's local IndexedDB. The editor auto-saves to IndexedDB roughly every second; refreshing the page, closing the tab, and reopening the browser all preserve your work.
What anonymous editing supports:
- Full editor functionality — create, edit, validate, and export a GTFS ZIP.
- Import an existing GTFS feed and round-trip it.
- Use the demo feed at /demo for testing or exploration.
What anonymous editing doesn't support:
- Multiple devices or browsers. Your work is tied to the one browser profile it was created in. Opening the editor on another laptop won't show it.
- Surviving a browser-data clear. If you clear site data, switch browsers, or open in incognito, the work is gone — there's no backup.
- Hosted publishing, analysis features beyond the Free tier, organization membership.
Signed-in editing
Sign in (or create a free account at the link in the top right) to bind your work to a cloud-synced account. With an account you get the same editor, plus:
- Cross-device sync. The feeds you save are visible on any browser you sign into.
- Snapshots. Every save can be promoted to a named snapshot you can browse and restore.
- Organizations. Agency and Enterprise plans support multi-user organizations where members share a set of feeds.
- Hosted publishing. Pro and above can publish to
feeds.gtfsx.com; see Hosted publishing.
What "Save" actually does
The Save button behaves slightly differently depending on whether you're anonymous or signed in, and this is the source of the most common confusion:
- Anonymous: Save is a no-op. Your work is already being auto-saved to local IndexedDB; there's nothing to push to the cloud because there's no cloud account to push to.
- Signed in, on an existing cloud feed: Save pushes the latest state up to the cloud. Until you click Save, the "Saved" indicator stays as "Unsaved changes."
- Signed in, on a feed that started anonymous and was never on the cloud: The first Save transfers the entire local-storage feed up to the cloud and creates a new server-backed project. From that moment on, the feed lives in the cloud and is treated as case 2 above. This is the transfer moment that wires an anonymous draft into your account; everything you do after that point is synced.
The practical takeaway: if you've been editing anonymously and want to keep the work, create an account and click Save. The auto-save to IndexedDB has been keeping it safe locally; the explicit Save promotes it to the cloud.
Tier limits
Saved feeds and snapshots have per-tier caps:
| Plan | Saved feeds | Snapshots / feed | Published feeds |
|---|---|---|---|
| Free | 3 | 5 | 0 (export & self-host) |
| Pro | 10 | 25 | 1 |
| Agency | Effectively unlimited | 50 | Unlimited |
| Enterprise | Custom | Custom | Custom |
If you hit the saved-feeds cap, deleting an existing feed frees up the slot. Anonymous editing doesn't count against the cap — only feeds explicitly saved to the cloud do.
Account management
- Sign in / sign out from the top-right of the editor. Email + password or magic-link by email; pick whichever you prefer at sign-in.
- Account settings at /account. Display name, email, password, organization membership.
- Billing at /account → Billing. Plan management is handled through Stripe; invoices and receipts are available in the billing portal.
Data export and deletion
- Export your feed. The editor's top-bar Export GTFS button produces a standards-compliant ZIP at any time, with or without an account. Your data is never locked up — even if you cancel your subscription, you can export the current state of every feed before doing so.
- Snapshot history. Snapshots are individually exportable from the Snapshots tab if you want a frozen copy of a past version.
- Delete a feed. Deleting a feed from the editor's feed list permanently removes it and all its snapshots from the cloud. Local IndexedDB caches in browsers that previously opened it will also be cleared on the next sync.
- Delete your account. Account deletion is a single action in /account: it cascade-deletes every feed, snapshot, and stored asset, immediately and without recovery. There's no grace period. If you need to retain any feed before deleting, export the GTFS first.
See also
- Quick start — the fastest way to put a feed together (works anonymously).
- Hosted publishing — what changes when a saved feed becomes a published feed.
- Import and export — the canonical way to move data in and out.
- Privacy policy — what GTFS·X stores about you.