Open Screenshot Generator CLI
Open-source CLI and editor for App Store and Google Play screenshots: 101 templates, agent layout, size checks and agent hookup
- 153 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI starts a Chromium browser and writes files into the project
- The desktop app can upload assets to App Store Connect and Google Play, which needs developer account access
Install
- Works in
Manual install
npx open-screenshot-generator installConnects the design tools to an agent. Claude Code also has a plugin via /plugin marketplace add dotnetdreamer/open-screenshot-generator.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI starts a Chromium browser and writes files into the project
- The desktop app can upload assets to App Store Connect and Google Play, which needs developer account access
This is third-party code. Review the repository files before installing.
What it does
Open Screenshot Generator makes screenshots and preview videos for the App Store and Google Play. You start from a template, put app screenshots in device frames, edit text, colors and layout, then export files at store sizes. There is a web editor, a desktop app and a CLI. The CLI runs through npx: doctor checks the environment, init creates a project, fill picks a template and places screenshots from a folder, render builds the images and verify checks them against store rules. It needs Node.js 20.12 or newer and Chrome, Edge or Chromium. npx open-screenshot-generator install connects the design tools to a coding agent, and Claude Code has a marketplace plugin with skills for store asset tasks. The editor has 101 templates (app screenshots, Apple Watch, Mac, preview videos, Google Play feature graphics), one layout for several languages, project versions, live co-editing and direct upload of finished files to App Store Connect and Google Play from the desktop app. An AI agent picks the template, places screenshots and drafts text.
Who it is for. Mobile developers and marketers preparing store listing assets without paid design tools.
Good fit when
- Before release you need store screenshots at the right sizes for App Store and Google Play
- One layout must ship in several languages with different text and shots
- An agent should pick a template and place screenshots from a `shots` folder
- Finished files should be checked against store rules with `verify`
Not a fit when
- You need ad banners outside store sizes: the tool is built for store assets
- You need a cloud team with no login: co-editing and cloud saving depend on an account
- There is no Chrome, Edge or Chromium: the CLI does not work without one
Example request
Build App Store screenshots from the shots folder, pick a suitable template, set the text in English and Russian and check sizes with verifyLimitations
The CLI needs Node.js 20.12 or newer and a Chromium-based browser. Video preview in the web version works in Chrome or Edge, and some features (upload to App Store Connect and Google Play, built-in and local AI providers, an agent in Claude Code or Codex) exist only in the desktop app. The desktop agent runs on your Claude or ChatGPT plan, so no API key is needed. Publishing to the stores from the desktop app needs developer account access that you grant yourself.
How to disable. The CLI runs through npx and leaves nothing installed. The Claude Code plugin is removed with /plugin. The desktop app uninstalls the usual way for your system, and projects stay local until you turn on cloud saving.
FAQ
Which commands does the CLI have?
doctor checks the environment, init creates a project, fill picks a template and places screenshots from a folder, render builds images and verify checks them against store rules. The full list is in cli/README.md.
How do I connect it to Claude Code?
Run npx open-screenshot-generator install or install the plugin: /plugin marketplace add dotnetdreamer/open-screenshot-generator, then /plugin install open-screenshot-generator@open-screenshot-generator.
Are there export limits or a watermark?
According to the project there are none: the app is free and open source with no watermark or export cap, works without an account and saves projects locally.
What does the AI agent do in the app?
It picks a template, places screenshots and drafts text. In the desktop app it runs in Claude Code or Codex on your plan, and in the web version with your own API key or through copy and paste.
Can I make preview videos?
Yes, from a screen recording. In the web version video export works in Chrome and Edge, and in the desktop app without that limit.
Discussion
No questions or reviews yet.
Related
CLI toolsApp Store Screenshots
app-store-screenshots
A skill that builds on Next.js an editor of marketing screenshots for the App Store and Google Play: a canvas, device frames, export
Screenshots and preview videos for the App Store and Google Play: the agent walks the app on a simulator, frames the shots and checks store requirements
A skill that builds in-app screen and element capture for a SwiftUI app and loops it across every locale for the App Store
The asc CLI manages builds, TestFlight and App Store Connect releases, returning results as tables or structured JSON.
A guard hook before an App Store or Google Play submit finds critical rejection risks and blocks the command until they are fixed.
A CLI and Claude Code plugin that find App Store and Google Play rejection causes before you submit, citing the rule for each.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Open Screenshot Generator (this card) | no | 153 | |
| App Store Screenshots | no | 7,924 | a screenshot preparation skill without an editor or CLI |
| App Store Connect CLI | no | 8,335 | App Store Connect operations and not asset design |
| App Store Preflight | no | 1,416 | a pre-submission app review check |
README in short
The README says the app makes store screenshots and preview videos and lists recent changes: the Codex agent and the new CLI. It then covers the workflow steps, features, a comparison with paid tools, a web versus desktop table, CLI commands and agent hookup.