Pack a collection of .chron events into a portable .chronpkg bundle — or unpack an existing bundle to inspect and download its contents. No code required.
Drop all the .chron files that belong in this bundle. Titles and IDs are read from each file automatically.
.chroncal file defines a custom calendar system — useful when your events use non-Gregorian or fictional date systems (e.g. Shire Reckoning, a Stardate system, or a fantasy calendar). Bundle one here so any viewer or tool receives the full date context alongside the events..chronverse file defines a fictional or alternate universe — its time scale, anchor points, and canon scopes. Bundle one if your events belong to a specific fictional setting (e.g. Middle-earth, the Star Wars galaxy, an alternate history).
This tool does not currently support bundling media assets. If you need to include images, datasets, or other files, open the downloaded .chronpkg in any ZIP editor (just rename it to .zip) and place your files in the assets/ directory shown below. An assets/README.md is included in every bundle as a placeholder and guide.
my-bundle.chronpkg ← ZIP archive, rename to .zip to open │ ├── manifest.json ← Required entry point ├── events/ │ ├── event-one.chron │ └── event-two.chron ├── calendars/ ← Optional .chroncal files │ └── shire-reckoning.chroncal ├── universes/ ← Optional .chronverse files │ └── tolkien-legendarium.chronverse └── assets/ ← Add media files here manually ├── images/ e.g. maps, illustrations └── datasets/ e.g. CSV, GeoJSON
Media files inside a bundle are referenced using the chronpkg:// URL scheme — e.g. chronpkg://images/map.jpg — which resolves relative to the assets/ directory.