For the administrator#
Settings → Website (admin) (only for administrators), and Admin in the top bar for everything else.
Sign-up#
Open (anyone can make an account) or Closed (the sign-up links disappear; existing accounts keep working).
Where films are made#
- On users' PCs (Studio Agent) — the default; each user's own keys pay.
- On this server — a worker on the server makes the films one at a time (start the
film_studio_workerservice). It is slower than a PC; 720p is quicker. - User by user — choose differently for single users.
Whose API keys pay for films made on the server#
- The server's own keys (
Film_Studio/.envon the server) with the most one film may cost. - Each user's own keys — entered by the user in Settings, kept encrypted (
SF_KEYS_SECRETinenv.webmust be set before users save keys), never shown, not visible in the Admin.
Other site settings (Admin → Site settings)#
- Films waiting per user — how many films one user may have waiting or running at once.
- A notice shown on every page, and more.
Activity#
Every action is logged: My activity for each user; the Admin sees all, including the cost of each step.
Fonts#
Settings → Fonts adds .ttf / .otf fonts for the film name (title card, thumbnails, Reels); on the server
only the Admin can, and the fonts are then there for everyone. A film that uses one takes it along to the PC
that makes it. Check that a font's licence allows it in videos.

Example pictures of the picture styles#
The style cards on a film's settings page show the same scene painted in every style once you have made them —
once, on your PC, before publish.bat:
.\run.bat styles --examples # 13 pictures; it shows the cost and asks first
They are kept in Film_Studio\assets\style_examples\; publish.bat (copy_film_maker.bat) takes them to the
website with git. Until then the cards show colours. --force paints them all again.
The Studio Agent download and its updates#
Settings → My PC → Download Studio Agent gives a ZIP with the agent and the film maker (about 3 MB) — made
from the website's own copy of the film maker, so run copy_film_maker.bat before each git push. It never
contains a key, a film or anything private. When a newer film maker reaches the website, every PC installed
from the download shows Update next to it; the agent then updates itself before its next film.
Signed updates. copy_film_maker.bat also signs each release with your private release key (made the first
time, kept only on your PC in %USERPROFILE%\.filmstudio\release_key — back it up). The public half,
release_key.pub, goes into git and into every download. An agent installs an update only when it carries this
signature over every file it puts in place, so a broken-into website could not send its own program to the PCs.
Until a release is signed, Settings → My PC says so and offers no Update. Without the private key the agents can
no longer be updated (they would need a fresh download).
Updating the website (Raspberry Pi)#
On your PC, one double-click: publish.bat in FILM_STUDIO_WEB. It copies and signs the film maker, runs a
quick check (stops if something is broken), asks what changed, commits and pushes. With PI_SSH=user@the-pi
in env.web it then updates the Pi over ssh as well (it may ask for the Pi's password).
On the Pi, one command (when publish.bat does not do it for you):
cd /home/FILM_STUDIO_WEB/FILM_STUDIO_WEB && bash deploy/update.sh
It copies the database first, then pulls, installs new packages only when the lists changed, applies database
changes, collects the website's files, restarts film_studio (and film_studio_worker if it is on) and checks
that the website answers. If it does not, it shows the last lines of the log.
Nightly database copy — once on the Pi:
sudo cp deploy/film_studio_backup.service deploy/film_studio_backup.timer /etc/systemd/system/
sudo systemctl daemon-reload && sudo systemctl enable --now film_studio_backup.timer
The copies go to backups/ (the last 30). Better on another disk or a USB stick: add
Environment=BACKUP_DIR=/media/usb/film_studio to the service. To bring one back: stop film_studio, copy
backups/db-<date>.sqlite3 over db.sqlite3, start it again.
Tests on GitHub: if the repository is on GitHub, .github/workflows/tests.yml runs the website's tests after
every push (small offline test films, no cost) and checks that the release is signed.