Manage Elgato Prompter scripts without Camera Hub lock-in.
A free local tool for Elgato Prompter creators. Import any text file, organize your library, and back up everything from a simple GUI or one command.
Camera Hub gives you no way to import scripts, rename them, or back them up. One reinstall and your library is gone. PrompterKit wraps the local Camera Hub data format so your scripts stay portable, inspectable, and recoverable.

Everything Camera Hub is missing
Elgato Prompter is great hardware. Camera Hub is not great software for managing a script library. PrompterKit wraps it with the tools every creator needs.
Import any text file
Drop a .txt or Markdown file onto the page. PrompterKit groups it into chapters (a blank line starts a new scroll point, a single line break stays inside one) and registers it with Camera Hub instantly. No copy-paste required.
Back up your library
The CLI archives every script to a zip file and restores the whole library after a Camera Hub update, a reinstall, or a move to a new computer. Replace-mode restore stages files first and rolls back the live library if the final swap fails.
Terminal-free guided setup
Use the plain-text AI-assisted install guide if you want an assistant to handle setup commands with your approval. After launch, the browser GUI handles daily script management.
| Feature | Camera Hub | PrompterKit |
|---|---|---|
| Import from a text file | — | ✓ |
| Import from Markdown | — | ✓ |
| Rename a script | — | ✓ |
| Delete a script | — | ✓ |
| Reorder your library | — | ✓ |
| Export to a text file | — | ✓ |
| Backup & restore via CLI | — | ✓ |
| Web interface for daily script management | — | ✓ |
Quick setup
PrompterKit requires Python 3.10 or later. Check with python3 --version. If Python is missing, install it from python.org.
Runs locally. No accounts, no telemetry, no cloud sync. Your scripts stay on your machine.
Use with care: PrompterKit edits local Camera Hub data files because Camera Hub does not provide import, export, or backup tools. Close Camera Hub before write operations and use PrompterKit at your own risk. The software is provided under the MIT License without warranty.
The simplest way in: ask ChatGPT, Claude, Codex, or another local coding assistant to walk you through setup. Point it at the structured assistant guide and approve each command as it runs.
The guide follows the GuideCheck standard for human-verifiable assistant guides, a plain-text format that keeps what you review identical to what an assistant executes. It includes a sidecar manifest and public hash record, and can be checked at guidecheck.org/verify.
Before any import, rename, delete, restore, or reindex operation, close Camera Hub and make a PrompterKit backup.
Open the assistant guide View evidence-
Download PrompterKit
git clone https://github.com/snapsynapse/prompter-kit.git cd prompter-kit
-
Create a local environment and install Flask
python3 -m venv .venv source .venv/bin/activate python3 -m pip install -r requirements-gui.txt
On Windows, activate with
.venv\Scripts\activate -
Close Camera Hub, then launch PrompterKit
python3 prompter_kit_gui.py
Your browser opens automatically at
http://127.0.0.1:5000
Using PrompterKit
Once PrompterKit is installed, here is how to start it and manage your library day to day.
-
Quit Camera Hub first PrompterKit and Camera Hub share the same local script files. Close Camera Hub before launching so the two never write at the same time.
-
Start the app Activate your environment, then run the GUI. Your browser opens automatically at
http://127.0.0.1:5000.source .venv/bin/activate python3 prompter_kit_gui.py
On Windows, activate with
.venv\Scripts\activate -
Import and organize your scripts Drop in any
.txtor Markdown file to add a script, then rename, reorder, or delete entries from the library list. The index stays normalized so Camera Hub reads the library cleanly. -
Back up your library Run a backup to archive every script to a zip. Keep it somewhere safe so a Camera Hub reinstall or a new computer never costs you your scripts.
-
Stop the server and reopen Camera Hub When you are done, press
Ctrl+Cin the terminal to stop PrompterKit, then reopen Camera Hub to record with your updated library.
Prefer the terminal? Every action is also a one-liner. The CLI is optional; the GUI covers daily use.
import script.txt --name "Episode 42"Import a text file as a new scriptexport --listSee all registered scriptsbackupArchive your whole library to a ziprestore backup.zipRestore from a backup archivedelete "Old Draft"Remove a script by namerename "Draft" "Episode 42 Final"Rename a scriptimport --restart script.txt --name "Live"Auto-stop Camera Hub, import, restart after success or failure
If the launch command does not work, one of these is usually why.
-
"can't open file '.../prompter_kit_gui.py': No such file or directory"
You are not inside the project folder. The clone created a
prompter-kitdirectory; move into it before launching:cd prompter-kit, then runpython3 prompter_kit_gui.py. Runlsfirst and confirm you seeprompter_kit_gui.pyin the listing. -
"No module named 'flask'"
The virtual environment is not active, or dependencies were never installed. Activate it with
source .venv/bin/activate(.venv\Scripts\activateon Windows), then runpython3 -m pip install -r requirements-gui.txt. -
"command not found: python3" or a version below 3.10
PrompterKit needs Python 3.10 or later. Check with
python3 --versionand install from python.org if it is missing or too old. -
"Address already in use" on port 5000
PrompterKit is probably already running in another terminal or browser tab. Close the other instance, or stop it with
Ctrl+C, then launch again. On macOS, AirPlay Receiver can also hold port 5000, so disable it in System Settings if needed. - Changes do not show up in Camera Hub Camera Hub reads the library only at startup. Quit Camera Hub before editing in PrompterKit, and reopen it afterward so it picks up the updated scripts.
Free and open source
I built PrompterKit because I needed it. After losing a library of scripts to a Camera Hub reinstall with no recovery path, I wrote the tool I wished existed. Now it's free for every creator who runs into the same wall.
MIT-licensed. No accounts, no subscriptions, no telemetry. Your scripts stay on your machine. The source is on GitHub and contributions are welcome.