Fix: App Store Screenshots Cannot Contain Alpha Channels (2026)

You just spent six hours wrestling with Xcode, finally pushed your build to TestFlight, and now you’re standing at the finish line: App Store Connect. You drag and drop your carefully crafted screenshots into the media manager, wait for the progress bar to finish, and then—red text. "One or more screenshots cannot contain alpha channels."

It’s infuriating. It feels like a relic of a bygone era of computing. In 2026, we have generative AI that can write entire apps from a prompt, yet Apple’s ingestion engine still chokes on a single transparency layer. It’s the developer equivalent of a "Check Engine" light that only comes on when you’re five minutes away from your destination.

The "alpha channel" error is a classic rite of passage for iOS developers. If you haven't hit it yet, you will. We’ve seen this happen to seasoned pros and first-time indies alike. The good news? It’s a five-second fix once you know where to click. The bad news? If you have 50 screenshots for different device sizes (iPhone 16 Pro Max, iPhone 8 Plus, iPad Pro 12.9"), doing this manually is a nightmare. This guide covers why this error exists, how to kill it instantly with macOS built-ins, and how to avoid it entirely using professional tools.

What is an Alpha Channel (And Why Does Apple Hate Them?)

To understand the fix, you need to understand the "why." In digital imaging, a standard image has three color channels: Red, Green, and Blue (RGB). An alpha channel is a fourth channel (RGBA) that represents transparency. It tells the rendering engine which parts of the image should be see-through and to what degree.

According to Apple's Official Screenshot Specifications, screenshots must be "flattened." This means the image must be opaque. No transparency, no semi-transparent shadows, no "empty" pixels.

So, why is Apple so stubborn about this in 2026? It comes down to visual consistency. The App Store UI shifts between Light Mode (white backgrounds) and Dark Mode (true black backgrounds). If you upload a screenshot with a transparent background, Apple’s system doesn't want to guess what color should show through. Without a flattened background, you could end up with "ghosting" effects or UI elements that look broken when the store's theme changes. To prevent this, Apple simply rejects anything that isn't a 24-bit PNG or a standard JPEG.

Despite rumors of Apple moving toward HEIC as the primary format for store assets, the 2026 standard remains firmly rooted in flattened PNGs and JPEGs. They want predictability. They want to know that your app looks exactly the same on a user’s phone as it does in the preview.

Method 1: The 'Panic Fix' Using macOS Preview

If you only have one or two screenshots triggering the error, don't bother opening Photoshop or Figma. You can fix this using the Preview app that’s already on your Mac. This is the fastest way to get past the error when you're in a rush to hit a submission deadline.

1. Open the image: Double-click your problematic screenshot to open it in Preview.
2. Export: Go to the top menu and select File > Export...
3. The Secret Box: Look at the bottom of the export dialog. You’ll see a dropdown for "Format" (set it to PNG). Below that, there is a checkbox labeled Alpha.
4. Uncheck it: Uncheck the Alpha box. You’ll notice the file size might change slightly. This is macOS stripping the transparency layer and "flattening" the image against a white background.
5. Save: Rename the file (or overwrite the old one) and upload it back to App Store Connect.

Why the 'Alpha' box is sometimes hidden

Sometimes, you’ll open the export dialog and the "Alpha" checkbox simply isn't there. This usually happens because the image doesn't actually contain any transparent pixels, but the file header still claims an alpha channel exists. macOS is smart enough to realize there’s nothing to strip, but App Store Connect isn't smart enough to ignore the header.

If the box is missing, the foolproof fallback is to change the Format dropdown from PNG to JPEG. JPEGs, by definition, cannot contain alpha channels. Set the quality to "Best" to avoid compression artifacts, save it, and upload. Apple accepts high-quality JPEGs for all screenshot slots in 2026.

The Simulator Trap: Why Your Screenshots Have Alpha Channels

You might be wondering: "I didn't add transparency. I just took a screenshot of the app. Why is this happening?"

The culprit is almost always the iOS Simulator. When you use the standard `Cmd + S` shortcut to save a screenshot from the simulator to your desktop, macOS tries to be "helpful." Because modern iPhones have rounded corners, the simulator includes transparency in those corner pixels to make the image look like a physical device on your desktop.

Worse, if you have "improve for Mac" settings enabled or if you’re capturing the simulator window using `Cmd + Shift + 4 + Spacebar`, macOS adds a drop shadow around the window. That shadow is entirely made of semi-transparent alpha channel pixels. When you drag that file into App Store Connect, the system sees the shadow and immediately flags the error.

Honestly, it’s a bit of a developer joke at this point. Apple’s own developer tool (the Simulator) creates files that Apple’s other developer tool (App Store Connect) refuses to accept. We’ve been complaining about this for years, and yet, here we are in 2026 still unchecking boxes manually. It’s a "developer rite of passage" to hit this error at least once per project. Don't feel bad; even the big teams at Meta and Google likely have a junior dev who forgets to strip the alpha channels once a year.

Method 2: Bulk Removal via Terminal (For Power Users)

If you're launching a localized app, you probably have 5 languages and 3 device sizes. That’s 150+ screenshots. Opening each one in Preview is a waste of your life. Instead, use the sips (Scriptable Image Processing System) command. It’s a powerful utility built into every Mac that can process images in bulk without you ever opening a GUI.

In macOS 15 and 16, the `sips` command is still the most efficient way to handle this. Open your Terminal, navigate to the folder containing your screenshots, and run the following command:

for i in *.png; do sips -s format png --setProperty formatOptions normal "$i" --out "${i%.png}_fixed.png"; done

What this command does:

• `for i in *.png`: It loops through every PNG file in the folder.
• `sips -s format png`: It tells the system to process the file as a PNG.
• `--setProperty formatOptions normal`: This is the magic flag. By setting the format option to "normal," it forces the removal of the alpha channel.
• `--out`: It saves a new version of the file so you don't accidentally ruin your originals.

If you want to be even more aggressive and just overwrite the original files (make sure you have a backup!), you can use:

sips -s format png --deleteProperty alpha *.png

This command specifically targets the alpha property and deletes it from every PNG in the directory. It’s fast, efficient, and makes you look like a wizard to any junior developers watching over your shoulder.

Method 3: Avoiding the Error with AppMockup

Manual screenshots—the kind you grab directly from the simulator—look amateur. In the 2026 App Store, users expect more. They expect "marketing assets," not just raw UI captures. This usually involves putting the app inside a device frame, adding a background gradient, and placing a headline at the top.

The problem is that building these in Figma or Photoshop often introduces alpha channels again. Every time you export a layer with a shadow or a transparent background, you risk the error. This is where AppMockup comes in. It’s designed specifically to bypass this manual labor.

When you use the "Create New Mockup" mode in AppMockup, the AI takes your raw screenshots and generates store-ready 2K PNGs. The key difference? The output is automatically "flattened." Because AppMockup is built specifically for App Store submissions, it ensures that every image is 100% compliant with Apple’s transparency rules.

Here’s how it works:

• You upload your raw (alpha-heavy) simulator shots.
• The AI generates a professional background (no transparency).
• It places your app inside a device frame (like the iPhone 16 Pro).
• It outputs a 2K resolution PNG that is already flattened.

By the time you download your ZIP file from AppMockup, the alpha channel issue is already solved. You can drag all 50 images into App Store Connect at once, and they’ll upload without a single error message. It turns a 20-minute "fix-it" task into a 2-minute "done" task.

Common Questions & Troubleshooting

Question	Answer
Can I just rename .png to .jpg?	No. Renaming the extension doesn't change the underlying file structure. You’ll just get a "File Format Mismatch" error instead.
Does Google Play have this rule?	Generally, Google is more relaxed, but they still recommend flattened images for better performance and consistency across Android's varied UI themes.
What if I use 8-bit PNGs?	8-bit PNGs (PNG-8) don't support full alpha channels (only simple binary transparency), but Apple still prefers 24-bit flattened PNGs. Stick to 24-bit.

What if I'm on Windows?

If you’re developing for iOS on a cross-platform framework like Flutter or React Native and you’re using a Windows machine, you won't have Preview or `sips`. In this case, use Paint.net or GIMP. When saving a PNG in GIMP, uncheck the "Save color values from transparent pixels" and "Alpha" options in the export dialog. Alternatively, using a web-based tool like AppMockup is the easiest way to handle this without needing macOS-specific software.

The "Ghost" Alpha Channel

Sometimes, even after unchecking the Alpha box, App Store Connect still complains. This usually happens if there is an embedded ICC profile or metadata that Apple’s parser misinterprets. If this happens, the "Nuclear Option" is to open the image, take a screenshot of the image itself (Cmd+Shift+4), and then use that new screenshot. It’s dirty, but it works because macOS screenshots of the screen are typically flattened by default if they don't include window shadows.

Beyond the Alpha Channel: Other Upload Errors to Watch For

Once you’ve cleared the alpha channel hurdle, don't get too comfortable. App Store Connect has several other "gotchas" that can ruin your day:

• Incorrect Dimensions: As of 2026, the 6.7" iPhone (1290 x 2796 pixels) is the primary requirement. If you’re off by even one pixel, the upload will fail.
• Wrong Color Space: Apple prefers Display P3 or sRGB. If you’re exporting in CMYK (common if you’re coming from a print design background), the colors will look "neon" or washed out on the store.
• Too Many Images: You’re limited to 10 screenshots per device size. Choose your best 10; don't try to show every single screen in your app.

In our experience, the best strategy is to automate as much as possible. Whether you use a Terminal script or a dedicated tool like AppMockup, the goal is to remove "human error" from the equation. You should be spending your time improving your app’s code, not unchecking "Alpha" boxes in a file dialog.

Final Thoughts

The "App Store screenshots cannot contain alpha channels" error is a minor annoyance, but it represents the broader friction of app distribution. Apple wants perfection, and they want it in a very specific format. By flattening your PNGs, stripping your simulator shadows, and ensuring your assets are store-compliant before you even open App Store Connect, you save yourself a massive amount of frustration.

To recap your options:

• Use Preview for a quick, one-off fix.
• Use Terminal (`sips`) for bulk processing if you're comfortable with the command line.
• Use AppMockup to generate professional, compliant assets from the start and avoid the error entirely.

Now, go get that app submitted. The 2026 App Store is waiting.