EXT. DISTRIBUTION — CONTINUOUS

Download

Builds live on the project’s GitHub Releases page — take the newest release’s file for your platform. Read this page before you click: during the beta the install is unusual in a few places, and we would rather you meet each surprise here than on your screen.

Get the latest release

Windows and macOS builds don’t always ship in the same release — use the newest release that carries your platform’s file.

Windows

LTX-Cinescript-Setup.exe · ~185 MB

Windows 10 or 11, 64-bit.
First launch downloads ~3.4 GB — a Python runtime the installer deliberately doesn’t bundle. It unpacks to roughly 6.5 GB; budget ~15 GB free disk. There’s a progress screen, and it resumes if the connection drops.
Local generation needs an NVIDIA GPU with 24 GB of VRAM (the app checks what the card reports). Model weights are a separate ~76 GB download on first use, with the size shown before you commit.
No suitable GPU? The app still works. Cloud (API) mode runs on any machine that meets the base requirements, using your own provider keys.

Download for Windows All releases

macOS

LTX-Cinescript-arm64.zip · ~700 MB

Apple Silicon only (M-series). There is no Intel build — on an Intel Mac the app will not run.
macOS 12 Monterey or newer.
The download is big on purpose — the Mac app bundles its Python runtime, so there is no multi-gigabyte first-run download. It fetches only a patched FFmpeg (~28 MB) once.
The built-in local engine is Windows-only today. On a Mac you generate through cloud providers with your own API keys — or on your own machine by pointing the app at a local ComfyUI install. Native Apple Silicon generation is being ported from upstream.
Unzip and drag LTX Cinescript to Applications (the app’s current on-disk name).

Download for macOS All releases

Linux: not supported — no official builds. You can build from source on the platforms that are.

THE WARNINGS YOU WILL SEE

Your OS will push back the first time. Here’s exactly what happens.

During the beta, neither platform’s build is OS-trusted yet. That is a certificate-paperwork problem, not a sign anything is wrong with the download — and we’d rather tell you before the dialog appears than have you find out from the dialog.

Windows: SmartScreen will warn you

The installer isn’t code-signed yet, so the first run shows a blue screen:

Windows protected your PC

Microsoft Defender SmartScreen prevented an unrecognized app from starting.

Click More info, then Run anyway.

That’s expected. SmartScreen reputation is tied to a code-signing certificate, so this warning stays until signing lands — it does not fade with downloads. Signing is planned; when it clears, the warning goes away on its own.

macOS: Gatekeeper blocks the first launch

Mac builds are signed with a Developer ID certificate but not yet notarized by Apple, so on first launch macOS says it “could not verify” the app is free of malware. Expected during the beta. To open it:

Extract the zip and drag LTX Cinescript to Applications.
Open it once and dismiss the warning.
Go to System Settings → Privacy & Security, scroll to Security, and click Open Anyway next to the Cinescript message. (On macOS 15 and later this is the only route — the old Control-click → Open shortcut no longer works for unnotarized apps.)
Confirm. macOS remembers the choice; you only do this once.

Notarization is coming — it’s waiting on an Apple Developer organization enrollment, not on anything in the code.

Verify your download (optional but recommended). Because the builds aren’t fully OS-trusted yet, the published checksum is how you confirm the file is what we built. GitHub shows a sha256:… digest next to every file on the release page — compare it against your download:

# Windows (PowerShell)
Get-FileHash .\LTX-Cinescript-Setup.exe -Algorithm SHA256

# macOS
shasum -a 256 LTX-Cinescript-arm64.zip

AFTER THE DOWNLOAD

First launch, both platforms

What each platform downloads, and when
	Windows	macOS (Apple Silicon)
Installer / download	~185 MB	~700 MB (Python runtime bundled)
First launch fetches	Python runtime, ~3.4 GB (unpacks to ~6.5 GB) + FFmpeg, 168 MB	FFmpeg only, ~28 MB
Local video generation	NVIDIA GPU with 24 GB VRAM; ~76 GB of model weights on first use	Not available — cloud providers only
Cloud (API) mode	Works with no GPU at all — bring your own API key for at least one provider

The two platforms deliberately don’t ship the same thing: the Windows installer is small and fetches its runtime on first launch; the Mac app carries its runtime inside the bundle. Expect a wait and a progress bar the first time on Windows; after that it starts normally. The FFmpeg fetch exists because the bundled copy predates a security fix — it’s checksum-verified, happens once, and carries no information about you (details).

First run asks: Local or API? Choose Local only on Windows with a 24 GB NVIDIA card. Everyone else picks API, then opens Settings → API Keys and adds a key for at least one provider — you need fewer keys than you’d think.

THE EASY WAY

Not technical? Let an AI assistant install it.

Hand the repository link to your AI assistant (Claude, ChatGPT, Cursor — anything that can read a link) and say:

Install Cinescript on my computer from
github.com/GenerativeCreations/ltx-cinescript — use the latest
release, not a source build.

The repository’s README carries step-by-step instructions addressed to the agent, including the OS warnings above and how to verify the install worked.