Built for Developers
Screenshot editor for developers
Add backgrounds, device frames, 3D effects, and animations to code, terminal, and app screenshots. Runs in your browser and is included in every Shots plan.
How developers use Shots
From README files to conference talks, make every screenshot count.
GitHub README images
Make your open source projects stand out with polished screenshots in README files. Add backgrounds and shadows to app screenshots that show off your work at its best.
Code snippet sharing
Share code screenshots on Twitter, LinkedIn, or dev blogs, with gradient backgrounds and device frames.
Terminal & CLI output
Turn raw terminal output into clean visuals for documentation and tutorials. Add macOS window frames and subtle shadows.
Technical blog posts
Create hero images and inline screenshots for dev.to, Hashnode, or your personal blog. Consistent styling across all your content.
Portfolio & case studies
Present your projects in 3D perspective mockups.
Demo videos & GIFs
Create animated walkthroughs of your apps with zoom, pan, and transition effects. Export as MP4 or GIF for issue trackers and pull requests.
Fits your workflow
No installs. The editor runs in your browser.
Paste from clipboard
Take a screenshot with your OS shortcut, then Cmd+V directly into the editor. No saving files first.
Drag & drop
Drag any image file from your file manager straight onto the canvas. Supports PNG, JPG, WebP.
One-click presets
Pick a preset that matches your style. Dark mode gradients, minimal whites, or vibrant colors.
Why developers choose Shots
Open source
Open source under Apache 2.0. Inspect the code, contribute, or self-host.
Privacy first
Editing runs in your browser. Imported images are not uploaded to edit them, and export compression returns the finished image without storing it.
Fast & lightweight
No heavy downloads or Electron apps. Just open a browser tab and start editing.
Automate it from CI
Parts of the workflow are also available over HTTP, with no API key. POST /api/screenshot captures a live URL as a PNG and POST /api/export recompresses an image, which is enough to regenerate README and docs images on every release rather than redrawing them.
Read the API documentation for runnable examples and the error-code table, the authentication and rate limit notes, or pull the machine-readable OpenAPI 3.1 specification.