Related Pages
download
Exporting Cursors
Export .cur, .ani, Base64 CSS code, frame PNG backups, or a full cursor set zip.
folder_copy
Cursor Projects and Sets
Name cursors, manage workspace items, assign roles, and export complete cursor sets.
help
Troubleshooting
Fix common editor issues with drawing, selections, importing, exporting, and local drafts.
The editor integrates a completely automated, local draft storage engine to safeguard your artwork. Changes are saved continuously in the background without needing to click a manual "Save" button.
⚠️ Critical Warning: Cache Clearing & Site Data Deletion
Because drafts are saved exclusively in your local browser sandbox, clearing your browser cache, wiping cookies and site data, or running browser cleaning utility programs will permanently and irreversibly delete your drafts.
There are no server-side accounts or cloud backups on the site. If you clear your history or delete site data before downloading an export, your design is gone forever.
How Local Storage Works
Cursor-pack imports save every selected cursor, size and the workspace manifest in one transaction. A storage or quota failure leaves the previous workspace intact. Source archives, INF text and original cursor files are not stored as draft shortcuts; the saved drafts contain editable artwork and editor metadata.
Undo import restores the previous workspace until your next artwork or metadata edit, another tab's incompatible save, or a reload. You can inspect cursors and switch sizes first. Undo is local to the current page session, not a permanent project history.
Saves check the workspace revision to prevent a stale tab from overwriting newer work. If a conflict appears, keep the tab open and export any unsaved artwork before reloading. A database-upgrade message means you should close older editor tabs and reload; do not clear site data to resolve it. Older cached editor versions cannot save after this database upgrade.
Unlike simple websites that save simple settings in short storage, the editor utilizes a modern, robust browser database to house complex cursor sets:
Your cursor pixels, layers, timeline frames, and timing arrays are stored in a dedicated local database (IndexedDB) on your device. Capacity depends on the browser, available disk space and storage policy. Quota failures are reported; keep downloaded backups.
The background autosave engine scans your workspace for changes and writes active drawings to the local database every 15 seconds whenever modifications are detected.
A window exit listener is wired to the browser's
beforeunloadevent. If you close your editor tab, navigate away, or reload the page with unsaved modifications, the editor commits a final database save instantly before letting the window close.Major Draft Hazards
Because drafts are tightly bound to the specific browser and sandbox where they were drawn, protect yourself from these common hazards:
cursorease-craftto your cleaning tool's whitelist.Safe Backup Best Practices
Never rely 100% on browser drafts for long-term project safety. Make it a routine habit to export backups at major milestones:
.cur,.ani, or full set.zip. Reimporting restores supported cursor artwork, sizes, timing and hotspots, but not the original editor layer structure or undo history.