If you automate your iOS releases with fastlane, you've probably tried frameit — the fastlane action that wraps your raw screenshots in device frames and adds marketing text. It's a clever tool, and for years it was the default answer for developers who wanted framed App Store screenshots without opening a design app.
But if you're searching for a fastlane frameit alternative, you already know the pain points: missing frames for new devices, ImageMagick setup issues, and a JSON-based text layout system that takes real trial and error. This post looks at where frameit struggles and what a modern replacement workflow looks like.
What Frameit Does Well #
Credit where it's due. Frameit fits naturally into a fastlane pipeline:
- It picks up screenshots produced by
fastlane snapshotautomatically. - It runs headlessly in CI, so framed screenshots can be regenerated on every release.
- It's free and open source.
If your screenshots are simple — one device frame, one caption, a solid background — and your devices are well supported, frameit can still do the job.
Where Frameit Falls Short #
1. Device frames lag behind Apple's hardware #
Frameit depends on a maintained catalog of device frame images. Every autumn, Apple ships new iPhones — and there's usually a gap before matching frames land in the catalog, if they arrive at all. If you want your screenshots to show the current flagship device the week your update ships, waiting on frame updates is a real cost.
Apple's requirements don't wait either: the current size matrix spans iPhone, iPad, Mac, Apple Watch, Apple TV, and Apple Vision Pro. See our complete App Store screenshot sizes guide for what App Store Connect expects today.
2. The ImageMagick dependency #
Frameit renders text through ImageMagick. That means a system-level dependency to install and keep working — font configuration, homebrew upgrades that break rendering, and CI images that need extra setup. Plenty of frameit debugging sessions end in fixing ImageMagick, not screenshots.
3. Layout by JSON, feedback by re-run #
Design decisions in frameit live in a Framefile.json: paddings, font sizes, colors, text positioning. There's no live preview — you edit numbers, re-run the command, open the output, and repeat. For a single caption that's tolerable. For a six-screenshot set in ten languages, it's slow, and getting text to sit well across different device aspect ratios takes a lot of iterations.
4. Framing is only one step #
Frameit frames images. It doesn't manage your caption translations, doesn't warn you when localized text overflows, and doesn't get the results into App Store Connect — you still need deliver configured correctly, or manual uploads. The full job — design, localize, export every size, upload in the right order — is bigger than framing.
What to Look For in a Frameit Alternative #
Based on what actually costs time in screenshot pipelines, a replacement should:
- Ship current device frames — including the newest iPhones, iPad, Mac, Apple Watch, Apple TV, and Vision Pro.
- Give visual feedback — direct manipulation instead of edit-JSON-and-re-run.
- Handle localization — manage caption text per locale and show you overflow before Apple's reviewers see it.
- Export every required size from one design, matching Apple's screenshot specifications.
- Upload to App Store Connect — all platforms and locales, in the correct order.
A Native Alternative: Screenshot Studio #
Screenshot Studio is a native Mac app built for exactly this workflow, and it pairs well with the fastlane tooling you already use:
- Keep
fastlane snapshotfor capturing raw screenshots — automated capture is still the right tool for that job. - Drop the captures into Screenshot Studio and design your framed set visually: current device frames, backgrounds, captions, with instant preview instead of JSON round-trips.
- Localize captions in the app — including AI-assisted translation — and see every locale rendered before you export. More on that workflow in how to create localized App Store screenshots.
- Export every device size automatically from one master design — no per-device export presets.
- Upload directly to App Store Connect for all platforms and locales, correctly ordered, without configuring
deliver.
There's no ImageMagick, no frame catalog to wait on, and no system dependencies to babysit. It's free to try, with a one-time purchase option instead of a subscription.
Frameit vs Screenshot Studio at a Glance #
| fastlane frameit | Screenshot Studio | |
|---|---|---|
| Interface | CLI + Framefile.json |
Native Mac app, visual editor |
| Preview | Re-run to see changes | Live |
| Device frames | Community catalog, can lag new devices | Current Apple devices, updated with releases |
| Dependencies | Ruby, fastlane, ImageMagick | None |
| Localization | Bring your own .strings, no overflow checks |
Built-in locale management + AI translation |
| Multi-size export | Per captured size | Every required size from one design |
| App Store Connect upload | Separate deliver setup |
Built in |
| CI automation | Yes | No — it's an interactive design tool |
| Price | Free, open source | Free to try, one-time purchase |
The honest trade-off: frameit can run unattended in CI; Screenshot Studio is an interactive tool. If regenerating framed screenshots on every automated build is a hard requirement, frameit (with its maintenance costs) still earns its place. If — like most teams — you redesign screenshots a few times a year and localize them often, the visual workflow is dramatically faster. Our hidden cost of App Store screenshots breakdown puts numbers on that.
Migrating From Frameit #
Moving over takes less time than a typical frameit debugging session:
- Keep your raw captures. Whatever
snapshot(or manual capture) produces is your input either way. - Recreate your layout once in Screenshot Studio using a template — background, frame, caption.
- Import or re-enter captions per locale, and let the app flag text that overflows at small sizes.
- Export or upload. Either export all sizes to disk, or push straight to App Store Connect.
From there, updating screenshots for a new release means swapping the captures and clicking export — not touching JSON.
Conclusion #
Frameit solved framing for a scriptable, CI-first world, and it's still fine for simple, stable setups. But if you've hit the frame-catalog lag, fought ImageMagick, or lost an afternoon nudging Framefile.json values, a purpose-built visual tool is the upgrade: current frames, live preview, built-in localization, and direct upload.
Try Screenshot Studio for free and see how long your next screenshot update takes — start with what an App Store screenshot generator does if you're new to the category.