App Store screenshot questions, answered.

Three steps: (1) Capture each screen in your app at the source resolution. (2) Composite each capture inside the right device frame for every store size you need. (3) Add captions, backdrops, and brand styling. ScreenStack automates all three — you point the SDK at a route, pick a backdrop in the editor, and the export gives you every store size as a PNG ready for upload.

Yes. The SDK runs in any Node or Dart CI environment — GitHub Actions, GitLab CI, FlightStack, or self-hosted. Add it to your build step, point it at your test users (stored encrypted in ScreenStack), and every CD run refreshes the marketing screenshots automatically.

No. ScreenStack exports PNGs at the right dimensions; you still upload them to App Store Connect or pipe them through fastlane deliver. The point is removing the manual Figma/Photoshop step between capture and store submission.

The two required iPhone sizes are 1320×2868 (iPhone 16 Pro Max, 6.9″ slot) and 1290×2796 (6.7″ slot, covers iPhone 15 Pro Max). iPad-supporting apps additionally need 2048×2732 (iPad Pro 12.9″). Full reference of every size on /screenshot-sizes.

Google Play accepts any 9:16 ratio image between 320 and 3840 pixels on the long edge for phone screenshots; 1080×1920 is the canonical phone size. Tablet apps additionally need 1200×1920 (7″) and 1920×1200 (10″). At least 2 phone screenshots are required to publish.

Apple requires both sizes if you target users on both devices. Practically, the 6.9″ slot (iPhone 16 Pro Max) is the new required minimum and many teams ship only that — Apple downsamples for older devices automatically. ScreenStack ships device profiles for both.

Yes. The screenstack_sdk package on pub.dev integrates with Flutter's integration_test harness — declare the screens you want captured in a screenstack.yml at your repo root and the SDK runs them on every CI build. Works on iOS, Android, and Flutter Web.

Yes. The @voostack/screenstack-sdk JavaScript package runs against any URL — including React Native's Metro bundler and native iOS apps wrapped in a web view. For pure native iOS, point the SDK at a web build or use the SDK's Playwright integration to capture from your app's URL.

The SDKs are open source on pub.dev (Flutter) and npm (JavaScript). The editor + compositing service is hosted; pricing is on /pricing.

Yes. In Flutter, wrap your widget with RepaintBoundary(key: ValueKey('food-card'), …) and set widgetKey: food-card in screenstack.yml — the SDK rasterizes only that widget, transparent outside its bounds. In JS, set kind: widget plus a clipSelector CSS selector — Playwright captures the element with omitBackground. The editor treats these as floating layers so a captured card can pop out of a device frame underneath.

Yes. The marketplace lets verified Studio sellers publish templates to the public gallery. Free templates clone into the buyer's project on click; paid templates route through Stripe Checkout with the buyer's purchase tracked end-to-end. Set up a seller payout account on the seller page in /app.

ScreenStack exports PNG files at the exact dimensions App Store Connect requires; you still upload them via App Store Connect or pipe them through fastlane deliver. We don't replace the submission flow — we replace the painful Figma/Photoshop step before it.

Free tier: 3 projects, 5 exports / month, every store size, 1 team member. Studio ($19/mo): unlimited projects + exports, Web Capture, FlightStack integration, unlimited team members. Studio Plus ($49/mo): everything in Studio plus 100 AI tokens/mo, priority capture queue, custom device profiles.

Yes. Subscriptions cancel at the end of the current billing period from the Manage Billing portal in your account. No long-term commitments.

Not yet — monthly only as of 2026. Annual pricing is on the roadmap.