Protect Your Library and Keep It Small¶
HeroQuest Card Creator keeps your working library in the browser profile or installed app copy you are using. The app asks the browser to treat that local data as important, but the browser still controls how local site storage is managed.
That means a .hqcc backup is the safety copy you control. If your cards, assets, and decks matter, export a backup regularly and keep the downloaded file somewhere outside the app.
Why backups matter¶
Browsers normally try to keep local site data, and the app requests extra protection where the browser supports it. That protection reduces the risk of automatic cleanup, but it is not the same as a backup.
Your local library can still disappear if browser data is cleared, a private window is closed, a different browser profile or app copy is used, or the browser decides it needs to recover space. Some browsers ask before granting stronger local-storage protection; others decide automatically based on how often and how recently you use the site.
For browser-specific site data settings, see:
- Chrome on-device site data help
- Edge cookies and site data help
- Safari website data help
- Firefox local site storage settings
For more technical background, see MDN's Storage API overview, MDN's storage quotas and cleanup guide, and web.dev's persistent storage guide.
Keep image files sensible¶
Large images make the local library and its backups heavier. Before uploading artwork, prepare the image for the job it needs to do:
- Use JPEG for full-card artwork, card backs, and other opaque background-style images.
- Keep PNG for images that need transparency, such as cut-out character art or icons.
- Avoid source images that are much larger than the card unless you need extra room for zooming and reframing.
- The card output is currently 750×1050, so a full-card image does not usually need to be many times larger than that.
- Smaller artwork windows and icons can usually use smaller source images than full-card backgrounds.
Image quality is a judgement call. A slightly compressed JPEG can be visually indistinguishable on a printed card while using much less space than the original file.
Use the app's asset tools¶
The Assets workspace includes tools that can help keep a library tidy:
- Convert to JPEG appears for selected PNG files that do not need transparency.
- Replace lets you swap one reusable image for a smaller prepared version without choosing that image again on every card.
- Asset details show dimensions and file size so you can spot unusually large uploads.
These tools help, but they do not replace preparing images before upload. If you already know an image is a full-card background with no transparency, saving an optimized JPEG before importing it is usually the cleanest path.
Practical routine¶
- Export a
.hqccbackup after substantial card, asset, or deck work. - Keep that backup outside the browser, such as in your normal documents, cloud drive, or external backup.
- Review very large assets in the Assets workspace.
- Replace oversized images with prepared versions where the visual result still looks right.
- Keep using the same browser profile or installed app copy unless you intentionally export and import your library somewhere else.
See Back Up and Restore Your Library for the backup workflow and Replace, Convert, and Delete Assets for asset replacement and conversion.