cinegram
Animated, narrated architecture diagrams from a Mermaid-compatible DSL. A
.dgm file is a Mermaid diagram plus scenario, view and interact blocks;
cinegram compiles it into a self-contained HTML page that plays.
uvx cinegram preview diagram.dgm -o out.html
uvx cinegram lint diagram.dgm --strict
uvx cinegram record diagram.dgm -o out.gif
pipx run cinegram …, pipx install cinegram and pip install cinegram all
work the same way.
What this package is
A launcher, not a copy of the compiler. cinegram itself is a single static Go
binary published on
GitHub releases; this package
downloads the one that matches your platform the first time you run it, checks
it against the release's SHA256SUMS, and executes it. There is no install
hook, so nothing can fail during pip install and then puzzle you later: a
failure can only happen at the moment you run the command, in front of you.
The version is pinned to this distribution's own version, so
uvx cinegram==0.3.0 runs exactly the v0.3.0 binary. Because the cache entry
is version-pinned, cinegram upgrade refuses to run under the launcher —
install a newer version instead (uvx cinegram@latest …, pip install -U cinegram).
Supported platforms: darwin-arm64, darwin-x64, linux-x64, linux-arm64,
win32-x64. Anything else gets a clear error naming the platform.
Cache
Binaries land in one directory per version:
| macOS, Linux | ~/.cinegram/bin/v<version>/cinegram-<os>-<arch> |
| Windows | %LOCALAPPDATA%\cinegram\bin\v<version>\cinegram-win32-x64.exe |
Delete the directory to force a fresh download.
Environment
| Variable | Effect |
|---|---|
CINEGRAM_BIN |
Run this binary and skip everything above — no download, no cache. |
CINEGRAM_CACHE_DIR |
Use this directory instead of the default cache root. |
CINEGRAM_DOWNLOAD_BASE |
Fetch from a mirror instead of GitHub releases; the launcher appends /v<version>/<asset>. For testing and internal mirrors — the checksum check still applies. |
Some subcommands need more than the binary: PNG frames and record need a
Chrome/Chromium ($CINEGRAM_CHROME), and --format mp4|webm needs ffmpeg
($CINEGRAM_FFMPEG). GIF recording needs nothing else.
More
- Documentation
- Source
- Also available as
npx cinegram, as a VS Code extension, and as a plain binary download.
Release files for cinegram 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cinegram-0.4.0.tar.gz | 6.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cinegram-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.9 kB
Release files / cinegram-0.4.0.tar.gz
| Download URL | cinegram-0.4.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
333854ff61084ff9e1b8c05a551691a9e953bd057d0657905d6b46ac670497b1
|
|
BLAKE2b-256 checksum How to use checksums |
3fbd14faea813f4c68babf1656e4fb90d7299625f48110c57b29408abdefae13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logRelease files / cinegram-0.4.0-py3-none-any.whl
| Download URL | cinegram-0.4.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e6bce3d49c319e5d3709cbcbbf3d31a3ccc3eb9b19dca1d6079842e533c6a52
|
|
BLAKE2b-256 checksum How to use checksums |
e04b103916b25734931e41497e325e92ae2dc2e90dad5b8711317cd266339ea2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency log