File Formats

The .CryptArt and .Crypt file formats - permanently future-proof project files

.CryptArt File Format

Overview

The .CryptArt file format is the universal project file for all CryptArtist Studio programs. It is a JSON file with the extension .CryptArt and the registered MIME type application/x-cryptartist-art.

Design Goals

The .CryptArt format was designed with one overriding goal: it must never need a base format upgrade. The envelope schema is stable forever. Any .CryptArt file ever created will always be readable by any version of CryptArtist Studio.

Key Principles

File Structure

{ "$cryptart": 1, "program": "media-mogul", "appVersion": "1.69.420", "data": { "workspace": "edit", "timeline": { ... }, "mediaPool": [ ... ] } }

Required Fields

Field Type Description
$cryptart number Format version (always 1, only increments on breaking changes)
program string Program ID (e.g., "media-mogul", "vibecode-worker")
data object Program-specific data (structure varies by program)

Recommended Fields

Field Type Description
appVersion string Version of CryptArtist Studio that created the file
name string Human-readable project name
description string Project description
author string Creator name
createdAt string (ISO-8601) Creation timestamp
updatedAt string (ISO-8601) Last modification timestamp

Backward Compatibility

The parser handles all historical .CryptArt file versions:

.Crypt File Format

Overview

The .Crypt file format (CryptArtist Crypt) is a collection container for multiple .CryptArt files with metadata, versioning, and organizational structure. A .Crypt file is fundamentally a ZIP archive with a specific internal directory structure and manifest.

File Structure

MyProject.Crypt (ZIP archive) ├── Memorial.txt (Manifest - metadata, versioning, credits) ├── Skeleton/ (Main .CryptArt project files) ├── Grave/ (Shared assets - images, audio, fonts) ├── Urn/ (Backups & version history) ├── Epitaph/ (Documentation - README, CHANGELOG, LICENSE) ├── Vault/ (Encrypted secrets - API keys, credentials) ├── Catacombs/ (Nested .Crypt files - sub-projects) ├── Reliquary/ (Curated collections - favorites, templates) ├── Soul/ (AI prompts & outputs) ├── LastWords/ (Log files - build, operations, errors, activity) └── Pyramid/ (Self-running bootstrap - Mummy agent + Curse traces)

Folder Descriptions

Folder Purpose Content
Skeleton/ Main project files Collection of .CryptArt files (the "bones" of the crypt)
Grave/ Shared assets Images, audio, fonts, brushes, textures, color palettes
Urn/ Backups & history Previous versions, exports, snapshots, archives
Epitaph/ Documentation README.md, CHANGELOG.md, LICENSE, guides, credits
Vault/ Encrypted secrets API keys, credentials, sensitive config
Catacombs/ Nested projects Sub-collections of .Crypt files (hierarchical organization)
Reliquary/ Curated selections Favorites, templates, presets, recommended files
Soul/ AI prompts & outputs Prompts used, AI responses, context, training data
LastWords/ Log files Build logs, operation logs, error logs, activity history
Pyramid/ Self-running bootstrap Mummy scripts (Mummy.bat, Mummy.ps1, Mummy.sh), config (Mummy.json), Curse/ templates

Forward Compatibility

The .Crypt format is designed to never need upgrading:

Why these formats matter: Your projects are future-proof. A .CryptArt file created today will be readable 10 years from now, even if the app has evolved dramatically. This is a core design principle of CryptArtist Studio.
CryptArtist Studio Logo