\n\nA prompt and a few keywords in. A narrated slideshow video out. Your keys, your machine, free.\n\n*Start contributing to the internet's enshittification today!*\n\n```sh\nnpx @gentbajko/slopify@latest\n```\n\nThat opens a browser at `http://127.0.0.1:6969`. Node 26 or newer is required.\n\nFor a persistent install that makes `slopify` available everywhere:\n\n```sh\nnpm install -g @gentbajko/slopify\nslopify\n```\n\nBoth commands launch the same local app.\n\nFor Docker on Linux with Node 26+, Docker Engine and the Docker Compose plugin, use\n`slopify --docker` or `npx @gentbajko/slopify@latest --docker`. It writes one\n`compose.yaml` and its `.env` under `~/.local/share/slopify/docker/slopify/` and starts\nSlopify at `http://127.0.0.1:6969`, restarting with Docker. Project files go to\n`Documents/Slopify/Projects` (`--projects-dir` to choose another, `--port` for the port); the\ndatabase, keys and logs stay private in the `slopify-data` volume.\n\nIf Claude Code, Codex or Gemini is installed, it asks once before setting up the host CLI\nbridge, a private helper that runs those CLIs on your machine with their existing logins.\nUse `--host-cli=off` for API keys only, or `--accept-host-cli` to approve without a prompt.\n\nUpdate with `npx @gentbajko/slopify@latest update`, Docker or not. Without Docker, `update`\nasks the running app to update itself, so it works only while Slopify is running (to just\nstart the newest version, run `npx @gentbajko/slopify@latest`). It waits for running\nwork, keeps a copy to go back to (the database, or a recovery volume in Docker), and puts\nthe previous version back if the new one doesn't start. Installations made by 2.5.0 or\nearlier are taken over as they are: same volume, same project folder. See the\n[Docker guide](https://github.com/GentBajko/slopify/blob/main/docs/docker.md) for details.\n\n## How to use it\n\n1. Add provider keys and voices in Settings. They stay in your local Slopify database.\n2. Write reusable article, image and thumbnail prompts in Prompts, using `{{keywords}}`\n where each video's subject belongs.\n3. In Play, build an autosaved setup across Content, Outputs, Style and Review. Supply\n or skip optional stages, preview subtitles, and inspect the estimated cost before Start.\n4. Follow total and per-stage progress in the project workspace. Pause unfinished work\n to change providers, add review checkpoints, or edit a paused or completed project as\n a retained revision. Saving does not rebuild until you explicitly ask.\n5. Save Play setups or project revisions as templates. Apply one to a fresh draft or\n schedule one-off, daily or weekly jobs with keyword variants and a spend ceiling.\n\nThe article is the only required output. Slopify can make a narrated or silent slideshow,\nan audio-only WAV, locally timed English subtitles, or just the intermediate results you\nselect. Uploaded and already completed outputs are reused when their inputs still match.\n\n## Inworld narration\n\nIn Settings, add the **Base64 credentials** from Inworld's API Keys page, then add an\nInworld voice ID (for example `Dennis`, or a voice from your workspace). In Play,\nchoose **Realtime TTS-2** or **Realtime TTS-2 Flash** and that voice.\n\nShort text streams immediately. TTS-2 text over 4,000 characters uses one async job,\nup to 100,000 characters; Inworld caps On-Demand accounts at 10,000. Audio becomes\navailable once that job finishes. Flash uses streamed parts of at most 4,000 characters.\nFor longer articles, select paragraph chunking. Successful status checks keep long jobs\nalive, and automatic polling/download retries reuse the accepted job. Pausing stops\nlocal requests; Inworld may still finish and bill an accepted job. Resuming after a\npause or app restart starts a new request for unfinished narration.\n\nSee [Inworld's async API](https://docs.inworld.ai/api-reference/ttsAPI/texttospeech/synthesize-speech-async)\nfor account limits. Both model IDs are bundled; Inworld's LLM catalogue does not list TTS models.\n\n## Options\n\n| Flag | Environment variable | Default |\n|---|---|---|\n| `--port` | `SLOPIFY_PORT` | `6969` |\n| `--host` | `SLOPIFY_HOST` | `127.0.0.1` |\n| `--data-dir` | `SLOPIFY_DATA_DIR` | `~/.slopify` |\n| `--projects-dir` (Docker only) | `SLOPIFY_DOCKER_PROJECTS_DIR` | remembered path; otherwise `/Slopify/Projects` (custom names: `/Slopify//Projects`); installs from before 3.0 keep `~/Slopify/Projects` |\n| `--no-open` | `SLOPIFY_NO_OPEN` | the browser opens |\n| `--docker` | — | run locally; with the flag, install or update the Docker version |\n| `update` | — | update the running app (it must be running), or the Docker installation if you have one |\n| — | `SLOPIFY_FFMPEG` | the bundled binary |\n\nThere is no login. Binding to anything but `127.0.0.1` hands the app and every key in\nit to whoever reaches the port, and the CLI says so on startup.\n\nNative installations keep `slopify.db`, `projects/`, `staging/` and `logs/` under\ntheir configured data directory. Docker places only projects in its\nremembered host folder; keep both that folder and the named private volume when\nbacking up an installation. The portable settings archive is not a project/history backup.\n\n## ffmpeg and the GPL\n\nNo separate FFmpeg installation is required. The `ffmpeg-static` dependency downloads\na prebuilt binary to `node_modules/ffmpeg-static/` at install time. Docker includes\nthe checked binary, licence and source notice in the image, ready on first launch.\n\nSlopify checks that ffmpeg runs before starting. If the install-time download is\nmissing, it downloads the same platform build into `/bin/`, keeping the\nlicence and source notice beside it. Later launches reuse that copy. If recovery\nfails, check your connection and antivirus quarantine, or choose your own executable.\n\nThat binary is a separate program, run as a child process with an argument array. It\nis licensed under the **GPL-3.0-or-later**. Slopify does not link against it, does not\nembed it, and does not distribute it inside this package; its licence text and the\nlocation of its corresponding source ship beside it in `ffmpeg-static`. Slopify's own\ncode is Apache-2.0 and stays Apache-2.0. Anyone redistributing the downloaded binary takes on the\nGPL's obligations for it, including offering that corresponding source.\n\nPoint `SLOPIFY_FFMPEG` at your own build to use that instead.\n\nIn Windows PowerShell:\n\n```powershell\n$env:SLOPIFY_FFMPEG = 'C:\\tools\\ffmpeg\\bin\\ffmpeg.exe'\nnpx @gentbajko/slopify@latest\n```\n\n## Telemetry\n\nSlopify sends anonymous counters to a collector: installs, projects created, stages\ncompleted, images and videos made, audio seconds, provider and model names, token\ncounts, and the time each of those happened. Every event carries a random id of its\nown and this machine's random id, and nothing else.\n\nNever your keys, prompts, keywords, titles, article text, filenames, or anything about\nyour machine. A notice says all of this the first time you run it, before the machine\nid exists, and the Usage screen shows you your own numbers at any time.\n\n## Supporting the project\n\nSlopify is free and always will be. If it is worth something to you, there is\n[Patreon](https://www.patreon.com/cw/GentBajko) and\n[Buy Me a Coffee](https://buymeacoffee.com/gentbajko). The people who do are listed\nin [SUPPORTERS.md](https://github.com/GentBajko/slopify/blob/main/SUPPORTERS.md).\n\n## Licence\n\nApache-2.0 (see LICENSE and NOTICE; keep the NOTICE when redistributing). The ffmpeg binary fetched at install time is a separate GPL-3.0-or-later program,\nas described above.\n\nSource, issues and the full guide: \n","readmeFilename":"README.md"}
![\"\"](\"https://slopify.stream/assets/favicon.svg\")
\n Slopify\n![\"\"](\"https://slopify.stream/assets/patreon-green.svg\")
Patreon\n · \n ![\"\"](\"https://slopify.stream/assets/buymeacoffee-green.svg\")
Buy Me a Coffee\n