# QPrompt is a Qt and QML teleprompter for creators who read on camera > QPrompt is a GPL licensed teleprompter application written in C++ and QML on the Qt and Kirigami frameworks, running on Linux, Windows, macOS and Android. It suits a creator who wants a script on a tablet beside a camera, and the project's own priority list explains why a requested feature can take a long time to land. **Cuperino/QPrompt-Teleprompter** — Teleprompter software for all video creators. Built with ease of use, productivity, control accuracy, and smooth performance in mind. - Repository: https://github.com/Cuperino/QPrompt-Teleprompter - Website: https://qprompt.app - Stars: 616 · Forks: 59 - Language: QML - License: GPL-3.0 - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/cuperino-qprompt-teleprompter ## A teleprompter that treats the tablet as the real target QPrompt is described as personal teleprompter software for video makers, built with ease of use, productivity and smooth performance in mind. The interesting part of the project description is the last clause of the first line of the project overview: it runs on Linux, Windows, macOS and Android. That platform list is the differentiator for most people. A teleprompter is a working tool used on set, next to a camera, usually on whatever tablet or laptop is to hand, and it is very often the only piece of software on that device that is not preinstalled. QPrompt is written in C++ and QML using the Qt and Kirigami frameworks, which is what makes a single interface work across desktop Linux, Windows, macOS and Android rather than being a desktop app with a separate phone edition bolted on. The project also calls it an editor as well as a prompter. The GitHub topics include text-editor alongside teleprompter, autocue and freesoftware, which tells you the script is something you write and revise in the application rather than something you paste in from elsewhere. For a creator working alone, this is a complete tool in one window: the script, the controls, and the same behaviour on the device in your hand and the machine at your desk. ## Where the binaries live, and where the newest features live The README points downloads at SourceForge rather than at GitHub releases, even though the GitHub release badge is present in the header. The primary download button resolves to the latest file on the SourceForge project, and the SourceForge project also carries a monthly download counter badge. Then there is the distribution question, and the project is explicit about it. Development builds are distributed through Patreon, and the documentation tells you that to get the latest features you should either get those builds over there or follow the instructions to build QPrompt yourself, with a link to BUILD.md in the repository. So there are two tiers: the public release, and a newer tier that supporters get. The reason is stated too. Patreon supporters get to vote on polls that determine where development focuses, and the priority list puts features voted for by supporters fifth, behind tech support, recent bug reports, code contributions and older bugs. That is a two tier support model, and it is worth being clear-eyed about when you adopt the project. The GPL v3 licence means the code is free and the public release is a complete application, but the newest features are a supporter benefit, and the roadmap is partly a paid poll. ## The priority list explains the release rhythm The README contains a rare thing in an open source project: an ordered statement of how the maintainer decides what to work on, including the honest admission that there is a large backlog of feature requests that are things that take time to develop. The order is support first, then the most recent bug reports, then code contributions, then older bugs that people keep asking about, then new features that Patreon supporters have voted for, then smaller tasks chosen for high demand, a skill the maintainer wants to work with, something quick to add, or a supporter request. Only then does the list mention contributing fixes upstream to the projects QPrompt depends on, and finally infrastructure maintenance, making builds and updating users. The builds take on average two days to make, according to the same section. That is a real constraint and it explains why releases are not weekly. For an adopter this matters in a practical way. If your requirement is a specific feature, the honest question is whether it sits in the top four buckets, because those are the ones that get attention without a vote. If it is a feature request, you are queueing behind everything else, and a supporter vote is what moves it. The project also says supporters include code contributors, documentation writers, translators, active users giving feedback, and beta testers, so the paid tier is not the only way to influence the queue. ## Translations are a separate work with its own licence The community translations setup is unusually thorough for an application of this size, and it is organised as its own project. The documentation points to a translation platform at l10n.cuperino.com where you pick a section of the project, find your language and contribute, with a badge showing the translated languages and another showing translation status for the v2 application. If your language is not there, the instruction is to file an issue at feedback.qprompt.com, which is a GitHub issue chooser pointing at the project's repository. The licence detail is the part that catches people out. The application code is GPL v3, but the translations are licensed under the Creative Commons Attribution 4.0 International licence. So a translation is not covered by the copyleft terms of the code it renders, and a translator is agreeing to CC BY 4.0 rather than to the GPL. That distinction is deliberate and sensible, and it matters if you are distributing a localised build. The copyleft obligation itself sits in the copyright section, which credits Javier O. Cordero Pérez for 2020 to 2026 and states that QPrompt is free software that you can redistribute and modify under the terms of the GNU General Public License version 3. There is also a separate COPYING.ASSETS file in the repository root, so the artwork and icons are evidently licensed apart from the source, another point to check before you ship a rebranded build. ## Repository layout: a Qt desktop app with an Android target and translations The repository layout tells you how the application is put together. There is an src directory for the C++ and QML sources, an android directory for the mobile target, a 3rdparty directory for bundled third party code, and a po directory holding the translation files that the translation platform feeds. The build system is CMake, with a CMakeLists.txt at the root, a cmake directory for toolchain and module files, a dist directory for packaging, a docs directory, icons for the artwork, and a vcpkg-configuration.json for dependency management through vcpkg. There is also a.pre-commit-config.yaml, so formatting and lint checks run before code lands, and a.env.android file, which suggests the Android build reads its configuration from environment variables rather than from a checked in secrets file. Other root files are worth noting: com.cuperino.qprompt.appdata.xml is the AppStream metadata, and com.cuperino.qprompt.desktop is the freedesktop desktop file. test_data holds test fixtures. setup.sh is a convenience script for preparing a development environment, and.gitmodules shows that at least one dependency comes in as a git submodule rather than through vcpkg. The application ids follow the reverse domain convention of the author, com.cuperino.qprompt, which is what makes the appstream and desktop entries match the Android package identity. ## What the documentation does not settle Some things you would want to know before committing to a teleprompter for production work are simply not in the repository documentation. The project documentation does not describe a text import format. If your script arrives as a Final XML, a Word document, a plain text file or a subtitle file, whether QPrompt reads it directly is not stated. Given the text-editor emphasis it is plausible you can paste and edit inside the application, but the format story is undocumented. It also does not document a mirror or prompt output over a network, a remote control from a phone, or an audio cue system. For a multi operator setup where one person runs the camera and another drives the script, that is a meaningful gap, and QPrompt's own naming joke acknowledges that teleprompter operators say a cue to the person on camera. The Android side has the same problem. The platform list includes Android, and the repository has an android directory and an .env.android file, but the documentation does not say where the Android build is published, whether it is signed for distribution through an app store, or which Android versions are supported. The SourceForge download button is the documented path, and the primary target is desktop. For a tool that will sit next to a camera for hours, the absence of documented export, backup and recovery behaviour for a long script is the other quiet risk, and the project documentation is silent on that too. ## Conclusion QPrompt fits a creator or a small production team that wants a script scrolling on a second screen or a tablet, values a desktop application that runs on Linux as well as Windows and macOS, and can accept the GPL v3 terms. It does not fit a team that needs a teleprompter with a guaranteed feature roadmap, since the project states that new features are queued behind support and bug fixes and are decided by supporter votes, and it does not fit an organisation that cannot accept GPL v3. Before adopting it, check that the release on SourceForge matches your platform, read BUILD.md if you intend to compile it, and confirm the Kirigami and Qt dependencies on your Android build, since the Android package is built separately from the desktop one. ## FAQ ### Where can I download QPrompt? The README points downloads at the SourceForge project, with a download button that resolves to the latest file there. Newer development builds are distributed to Patreon supporters, and you can also build from source using the instructions in BUILD.md. ### Does QPrompt run on Android? The README states that QPrompt runs on Linux, Windows, macOS and Android, and the repository contains an android directory and an .env.android file. The documentation does not say where the Android build is published or which Android versions are supported. ### How do new feature requests get prioritised in QPrompt? The README lists an explicit order, starting with tech support, then the most recent bug reports, then code contributions and older bugs, and only then new features voted for by Patreon supporters, with smaller tasks and upstream fixes further down. ### What licence covers QPrompt and its translations? The application code is under the GNU General Public License version 3, while the translations are licensed under Creative Commons Attribution 4.0 International. The repository also carries a separate COPYING.ASSETS file for the artwork. ## Sources - [Cuperino/QPrompt-Teleprompter on GitHub](https://github.com/Cuperino/QPrompt-Teleprompter) - [License: GPL-3.0](https://github.com/Cuperino/QPrompt-Teleprompter/blob/main/LICENSE) - [Project website](https://qprompt.app) - [README](https://github.com/Cuperino/QPrompt-Teleprompter/blob/main/README.md) - [Releases](https://github.com/Cuperino/QPrompt-Teleprompter/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/cuperino-qprompt-teleprompter