Skip to main content
Black Friday 50% off all subscriptions, 33% off Lifetime. Until Dec 1. Get the deal
← Tool Comparisons

Developer resources

Fastlane Frameit Alternative (2026): Import Snapshot Output As Is

A Fastlane Frameit alternative: import your fastlane snapshot or screengrab folder as is, then frame, localize and upload to App Store Connect. No ImageMagick.

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 snapshot automatically.
  • 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:

  1. Ship current device frames — including the newest iPhones, iPad, Mac, Apple Watch, Apple TV, and Vision Pro.
  2. Give visual feedback — direct manipulation instead of edit-JSON-and-re-run.
  3. Handle localization — manage caption text per locale and show you overflow before Apple's reviewers see it.
  4. Export every required size from one design, matching Apple's screenshot specifications.
  5. 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 snapshot for capturing raw screenshots — automated capture is still the right tool for that job.
  • Import snapshot's output folder as is. Screenshot Studio reads the language from each folder and the device from each file name, so every screenshot lands on the right platform, in the right language and slot.
  • 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, and Pro comes as a subscription or as a one-time lifetime unlock.

Frameit vs Screenshot Studio at a Glance #

fastlane frameit Screenshot Studio
Interface CLI + Framefile.json Native Mac app, visual editor
Snapshot output Frames it in place Imports the whole folder, every language
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; Pro subscription or lifetime unlock

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.


Importing Your Snapshot Output #

On the Mac, the import takes the folder fastlane writes, with no renaming:

  1. Run fastlane snapshot as usual. By default it writes to fastlane/screenshots/, one folder per language.
  2. Choose File › Import Screenshots from Folder… (⇧⌘I) in Screenshot Studio, or Import from Folder… on an empty platform, and pick that folder.
  3. Check the summary. The sheet shows one line per platform: how many screenshots go in, and in which languages. Platforms and languages the project doesn't have yet are added. If you captured several iPhones, you pick which device to use, and if you captured light and dark, or portrait and landscape, you pick which one.
  4. Choose what happens to filled slots. Replace them, or only fill the empty ones.

Screengrab works the same way: point the import at fastlane/metadata/android/, or at a folder holding both outputs, and the Android screenshots go to the Android platform. Files you name yourself, like ios-de-portrait-01-Home.png, import too.


Migrating From Frameit #

Moving over takes less time than a typical frameit debugging session:

  1. Import your snapshot folder. Whatever snapshot (or manual capture) produces is your input either way.
  2. Recreate your layout once in Screenshot Studio using a template — background, frame, caption.
  3. Import or re-enter captions per locale, and let the app flag text that overflows at small sizes.
  4. 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 re-running snapshot, importing the folder with Replace, 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 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, or see every comparison.

Frequently Asked Questions

What is a Fastlane Frameit alternative?

A Fastlane Frameit alternative replaces the ImageMagick framing step after fastlane snapshot. You keep snapshot for capture, then use a screenshot app to add frames, captions, every App Store size, and upload to App Store Connect.

Can I still use fastlane snapshot with Screenshot Studio?

Yes. Snapshot (or the simulator) still captures the raw screens, and the Mac app imports snapshot's output folder as is: each screenshot goes to the right platform, language and slot. Screenshot Studio then takes over framing, localization, size export, and App Store Connect upload — the parts Frameit and a frame catalog used to handle.

Does Screenshot Studio import fastlane screengrab screenshots?

Yes. Choose the folder that holds your screengrab output, or one with both snapshot and screengrab output, and the iOS and Android screenshots each go to their own platform.

Why do developers switch from Frameit?

New iPhones ship without Frameit frames for months, ImageMagick setup breaks in CI, and JSON text layout is slow to iterate. A native Mac app updates frames with the OS and exports every required size from one design.

Developer resources

Retire your frameit pipeline

Keep fastlane snapshot for capture — import its folder, then frame, localize, export every size, and upload to App Store Connect in Screenshot Studio. No ImageMagick, no frame catalog to wait on.