Frequently Asked Questions
Short, direct answers to questions we hear most often. Can't find what you're looking for? Get in touch.
Frequently Asked Questions
Product & Features
What is Screenshots.live?
Screenshots.live is an automated app store screenshot generator with a visual drag-and-drop editor and a REST API. Design a template once and render it for every iPhone, iPad, and Android size in every locale via one API call. Free tier includes 50 renders/month.
Do I need design skills to use Screenshots.live?
No — the visual editor handles layout, device frames, and locale fan-out automatically. You drop in copy and an app screenshot; the template handles the rest. Pre-built starter templates are available in the Template Library if you want to skip the blank-canvas problem entirely.
Which platforms and device sizes are supported?
Screenshots.live supports every current App Store size (iPhone 6.5", 6.7", iPad 12.9", 11") and every Google Play size (Android phone, 7" tablet, 10" tablet). One template renders for all of them automatically — no manual resizing per device.
Which locales does the rendering pipeline support?
Any Unicode locale — the renderer accepts any language string in your YAML config, including RTL scripts (Arabic, Hebrew). The visual editor exposes 13 UI locales: English, German, Spanish, Italian, Vietnamese, French, Portuguese, Polish, Dutch, Russian, Swedish, Norwegian, Finnish.
Can I upload custom fonts?
Yes — upload TTF, OTF, WOFF, or WOFF2 fonts via the editor or API. Standard tier includes multiple custom fonts; Pro tier raises the limit. Fonts are scoped to your account and used directly in render output without sub-licensing concerns.
Can my team share templates?
Yes — templates are owned by an account and accessible by every team member with API key access. Use Template Porting to clone templates between projects, or share API keys for shared rendering pipelines. SSO and seat-based pricing are on the roadmap.
Can I A/B test screenshots with Screenshots.live?
Yes — render multiple variants of the same template by swapping YAML variables, then upload each variant to App Store Connect's product page experiments. Screenshots.live owns the rendering side; A/B-test orchestration uses Apple Search Ads or App Store Connect tooling.
Pricing & Plans
How does pricing work?
Three tiers: Trial (free, 50 renders/month), Standard (paid monthly or yearly), and Pro (highest limits + priority support). All tiers include the visual editor, API access, and multi-locale rendering. EUR-priced. Annual billing saves up to ~20%. See the pricing page for current rates.
Is there a free tier?
Yes — the Trial tier is free forever and includes 50 renders per month, the visual editor, API access, and multi-platform rendering. No credit card required to start. Upgrade only when you outgrow the limits.
API & Configuration
What are the API rate limits?
Rate limits are per tier and per API key. Trial allows up to 50 renders/month at modest concurrency; Standard and Pro have substantially higher monthly caps and concurrency. The render API returns 429 with a `Retry-After` header when limits are hit. Exact numbers are on the pricing page.
How do I manage API keys?
API keys are created in the dashboard and prefixed with `sa_live_`. Each key authenticates template CRUD, item CRUD, and render dispatch under the same scope. Rotate keys by creating a new one and revoking the old. Store them as CI secrets — never commit them to source control.
What is the YAML scaffold and why use it?
Each template can export a YAML scaffold listing every dynamic variable. You edit the scaffold (titles, body copy, app screenshot paths) and POST it to the render API. The YAML is version-controllable, readable in PR reviews, and can be generated by AI agents — ideal for CI/CD.
Can I render arbitrary HTML inside a template?
Yes — the `Html` item type renders sandboxed HTML/CSS at a specified position on the canvas. Useful for rich text formatting, gradient backgrounds, and SVG illustrations. The HTML is rendered server-side via headless Chromium, so you get reliable cross-platform output.
Are there webhooks for render events?
Yes — register a webhook URL in your account settings and receive POST callbacks for `render.completed` and `render.failed` events. Payloads include the render ID, status, output URLs, and your custom metadata. Useful for triggering downstream uploads to App Store Connect.
Are there limits on canvas size or item count?
Custom canvas sizes go up to 2560 × 5120 pixels. Items per template are tier-based (Trial: limited; Standard/Pro: substantially higher). The renderer handles dozens of layered items per screen without performance issues; very large designs may render slower.
Integrations
Does Screenshots.live integrate with Fastlane?
Yes — install the official `fastlane-plugin-screenshotslive` from RubyGems, set your API key as an environment variable, and call `render_screenshots_live` from your `Fastfile`. The plugin downloads the rendered images so they can be uploaded to App Store Connect via Fastlane's `deliver`.
Can I render screenshots from GitHub Actions or other CI?
Yes — use the official `screenshots-live/render-screenshots-action` for GitHub Actions, or call the REST API directly from any CI (Bitrise, CircleCI, GitLab CI, Jenkins). The render endpoint accepts a YAML body and returns rendered images either inline or via signed URLs.
How is this different from Fastlane frameit?
Fastlane frameit is a Ruby CLI that adds device frames to existing PNGs. Screenshots.live owns the entire pipeline: visual editor, dynamic templates, multi-locale fan-out, and a REST API. Use frameit for quick framing of existing images; use Screenshots.live to design and generate at scale.
How is this different from AppMockUp?
AppMockUp is a free browser editor for one-off screenshots, no API. Screenshots.live targets teams who need automation: REST API, Fastlane integration, GitHub Action, dynamic templates with variables, and 13-locale UI. Pick AppMockUp for ad-hoc; pick Screenshots.live for production pipelines.
Is any part of Screenshots.live open source?
The integrations are open: `screenshots-live/render-screenshots-action` (GitHub Action) and `Screenshots-Live/fastlane-plugin-screenshotslive` (Fastlane plugin) are both MIT-licensed on GitHub. The core rendering service is proprietary.
Privacy, Compliance & Support
Where are rendered images stored?
Renders are stored in our object storage (Hetzner S3) and referenced by signed URLs returned in the API response. Free tier renders expire after 24 hours; paid tiers retain renders for 30 days. You can also download renders directly via the API to your own storage.
Is Screenshots.live GDPR-compliant?
Yes — Screenshots.live operates from Germany, hosts customer data on EU infrastructure, and signs DPAs on request. Renders contain no PII unless you put it there. Account data is processed under GDPR Article 6(1)(b) (contract). See the Privacy Policy and Imprint pages for full detail.
Who owns the rendered screenshots?
You do. Anything you upload (images, fonts, copy) and anything rendered from your templates belongs to you. Screenshots.live's terms grant a limited license only to operate the rendering pipeline. There are no clauses claiming ownership of customer-uploaded creative.
How do I get support?
Email support@screenshots.live or the founder directly via the contact form. Standard tier gets best-effort support; Pro tier gets priority response times. Bug reports and feature requests can also be filed on the public GitHub repos for the Fastlane plugin and GitHub Action.