Skip to main content

Work with files and storage

Your Markdown is canonical. Qontent Tube stores script bytes outside its relational index so the files remain portable and usable with the tools you already prefer.

Default local storage​

The desktop and local Bun runtimes default to <user-home>/.qontent-tube:

.qontent-tube/
├── audio/
├── documents/
│   └── <project-slug>/
│       └── script.md
└── qontent-tube.sqlite

Choose another absolute directory under Rosters & presets → Local content storage. Qontent Tube validates and creates it immediately, but the local API must restart before the new location becomes active. Existing files are not moved automatically.

Capture files​

A script can have a <script>.capture.yaml sidecar beside it. If you use AI adaptation, adaptations/ keeps the review history and compositions/ keeps animations, inside the project. Imported media stays private in your content folder. Media files inside a project folder are listed in Assets as read-only, and change only on disk.

Edit with another tool​

Add or update Markdown directly under <content-directory>/documents/<project-slug>/, then select the project or use its Refresh action.

Only safe, top-level .md files are discovered. Qontent Tube ignores nested files, symbolic links, temporary editor files, non-Markdown files, and ambiguous case-only duplicates.

Understand reconciliation​

  • A new valid Markdown file appears as a new script.
  • A malformed Markdown file is still preserved and opened with structural guidance.
  • An external content edit advances the server revision.
  • A clean editor reloads the changed source.
  • An unsaved browser draft is kept and shown as a conflict instead of being overwritten.
  • A removed file stays visible as missing so its identity and audio history are not silently discarded.

Restore a missing file with the same name and refresh to reconnect it. An external rename appears as one missing script and one newly discovered script; Qontent Tube does not guess that they are the same document.

Reconciliation never rewrites the files it observes. If storage cannot be listed safely, the last known project tree remains unchanged.