Search for a feature, task, or issue, or browse guides by topic.
Start with the feature you are using.
Expand a question to see steps and feature boundaries.
Create your first ranking and understand where data is stored
Rankings are stored in the current browser, so you can create and edit locally without signing in.
Projects, Library cards, tags, comments, versions, and images are stored in this browser's IndexedDB, which is the authoritative source.
Content is only sent to the cloud when you publish, upload a template, or create a cloud backup. Signing in does not automatically sync the workspace to other devices.
Do not clear site data to free space before exporting a .tierworld workspace backup.
Creating projects, editing rankings, managing the Library, and exporting PNG, HTML, or .tierproject files do not require an account.
Template uploads, publication management, cloud publishing, Drive backups, feedback, and subscription management require sign-in.
Mobile uses bottom navigation, drawers, and shorter flows, while desktop exposes fuller sidebars and toolbars. Both use data in the same browser.
Keep the page in the foreground while importing many images, especially on mobile devices where the browser may suspend a tab.
Create, organize, import, and restore projects
A Project stores its title, tiers, display settings, and card positions. The Library stores reusable core cards, covers, tags, and comments.
One Library card can appear in several projects. Changes to its core content are available to those projects, except for frozen version snapshots.
The project directory supports name search, sorting, grid or list views, and favorites. Project details let you adjust names and descriptions.
A deleted project first moves to the project trash. You can restore it during the retention period; permanently deleted projects cannot be recovered by Tierworld.
Export a .tierproject file or .tierworld workspace backup before permanently deleting a project.
A .tierproject is an editable project archive containing ranking data, cards, tags, versions, trash, and media. It is a ZIP archive and should keep its .tierproject extension.
The importer validates versions, references, media sizes, and completeness before committing any changes.
Tiers, cards, drag and drop, bulk actions, and versions
Cards can move between the asset pool, the same tier, and other tiers. The row menu changes labels and colors, reorders rows, or removes a row.
When deleting a row, choose where its cards should go in the confirmation dialog.
Select a card to edit its name, replace or crop its cover, assign tags, and write rich-text comments.
Library card tags and comments can be reused across projects. Template snapshots become global Library cards only when explicitly saved there.
Enter multi-select mode, choose cards, and use the bulk toolbar to move them, apply tags, manage collections, or delete them.
Exit multi-select after an operation to avoid changing the selection accidentally.
Editor search narrows visible cards by name, and tag controls refine the result. Clear both the search and tag filters if a card appears to be missing.
Undo and redo are held in editor memory and reset when the page refreshes, the project changes, an import replaces it, or a version is restored.
Version history saves persistent project snapshots. Tierworld creates a checkpoint before restoring an earlier version.
Read-only mode disables actions that change project structure or card content. Turn it off to resume editing.
Reusable cards, collections, tags, and trash
Select one or more Library cards and add them to a project. Tierworld creates project branches that continue to reference the same Library core content.
Deleting a card from one project does not delete its Library original.
Use Collections for groups such as a source, topic, or asset pack; a card can belong to several Collections. Use tags to describe people, works, traits, or states and to search or filter.
Deleting a Collection removes only its membership links, not its cards.
The Library supports Grid, Album, and List layouts, plus search, tags, sorting, and grouping. These controls affect only the current view.
Deleted Library core cards enter a shared trash and remain for 30 days. Their details show which projects use them, and restoring repairs related references.
Permanently deleting a core card can also remove unfrozen project cards that still reference it.
Tierworld processes local images in small batches, generates thumbnails, then writes them to IndexedDB. A failed job is rolled back rather than reported as partially successful.
Avoid closing the tab, using a browser mode that freezes pages, or clearing site data during import.
Find, import, and publish asset packs
Open a template's details from search, categories, or tags, then save it to the Library or start a ranking directly.
Saving creates a Collection and reusable cards; starting directly creates an independent Project.
An Asset Pack becomes independent local data when downloaded. An online update or removal does not automatically change your Collection or Project.
Choose a Library Collection, select cards, fill in its details, category, and tags, review the preview, then submit it. Only upload assets you are permitted to use.
Saving to the Library validates and commits as one operation. Starting a ranking creates a project and import task first, then fills in images card by card; incomplete tasks remain in the local workspace.
PNG, HTML, project files, and web publishing
PNG is a static image. Single-file HTML works offline and retains card details, tags, comments, theme switching, and ranking browsing. A .tierproject preserves an editable project.
HTML and PNG only include cards assigned to tiers, not the asset pool or project trash.
Exported HTML uses UTF-8 and has no dependency on Tierworld, Next.js, or external fonts. Send it to anyone and open it in a modern browser.
Private uses private storage and an authorized preview flow. Unlisted and Public use stable share links. Public pages are not automatically included in a community or template directory.
PNG exports on the Free plan include a Tierworld watermark. Supporters can disable it after their entitlement is confirmed.
Local storage, workspace migration, and Drive backups
A .tierworld archive contains every local project, Library card, tag, version, trash item, and media file. A .tierproject is for one editable project. Both may contain private content.
Merge writes records that are missing locally and preserves existing records with the same key. Replace clears the current workspace and writes the backup snapshot.
Replace is destructive. Export the current workspace and safely retain the backup before proceeding.
Google Drive uploads or restores a current .tierworld workspace snapshot manually. It is not two-way real-time sync, and IndexedDB remains the authoritative source for this browser.
Saved projects, cards, and media in IndexedDB work without a network. Templates, sign-in, web publishing, feedback, subscriptions, and Drive backups require one.
Browser quotas, private-mode limits, system cleanup, or terminated tabs can cause local writes to fail. Tierworld displays errors but cannot bypass browser storage limits.
Sign-in, subscriptions, privacy, and feedback
Signing in does not upload or take ownership of local Projects and Library data. Data is transferred only when you actively publish, upload templates, or back up to the cloud.
Supporter renews at US$2.99 per month. Stripe manages checkout, payment methods, invoices, and cancellation; Tierworld never stores full card numbers.
Local content is isolated by browser profile and site origin. A different browser, private window, domain, or cleared site data does not show the same IndexedDB.
Describe the page, sequence of actions, expected result, actual result, and whether the issue is repeatable. Diagnostic reports are generated and attached only when you choose, and do not include project text or images.
Community comments and likes, cross-device workspace sync, and more advanced ranking tools remain future work. The help center describes only capabilities confirmed by the current code and product documentation.