Guide · 7 min read
App Clips Install Conversion: When a 10MB Experience Earns More Full Installs Than a Direct Link
App Clips let users run a focused slice of your app in seconds — no download, no sign-in, no friction at the entry point. Apple surfaces Clip cards in App Store Search results, Safari Smart App Banners, QR codes, NFC tags, and Maps listings. For the right app with the right core flow, a Clip converts roughly 18–22% of openers into full installs. The question isn't whether Clips work — it's whether your app's most valuable action fits inside 10MB and 30 seconds.
App Clip cards in App Store Search — a second listing most developers leave unconfigured
An App Clip card appears directly below your main App Store listing in search results — a second entry labeled "Open" instead of "Get," launching your Clip without requiring an install. This second impression is completely separate from your primary listing's impression count, and it's configurable: you link a Clip experience URL to the App Store Search invocation type in App Store Connect. If you haven't done this, users searching for your category see only one result from your app where they could see two.
The card shows your app icon, a title, and a subtitle specific to the Clip experience — not the subtitle field on your main listing. This per-experience subtitle is the only copy real estate the card gives you, so write it to answer one question: what happens in the next 30 seconds when they tap Open? "Get directions and order at the table" outperforms "Discover our full restaurant experience." For the relationship between your main listing's subtitle and search ranking, the breakdown of App Store subtitle vs. promotional text covers when each field earns more.
The 10MB budget: a product constraint, not a technical one
Every App Clip must ship under 10MB — and that limit is measured after iOS system frameworks are deducted, leaving the usable budget for your actual code and assets closer to 3–6MB depending on your dependencies. This forces a decision that most app design processes never make explicit: what is the single most valuable action in this app? The 10MB constraint is not a technical puzzle to optimize around — it's a filter that identifies whether your Clip concept is well-defined enough to build.
The flows that fit the budget share two properties: a single primary action (scan, pay, look up, book) and no mandatory account creation before that action delivers its result. The flows that don't fit usually involve onboarding sequences, multi-screen navigation, or features that depend on persistent local state across sessions. A Clip that launches and immediately prompts a full install because "the full experience requires the app" has already failed — it's functioning as an expensive redirect, not a sample of genuine value.
Which flow to expose: conversion math differs by surface type
The Clip flows that convert 18–22% of openers to full installs share one observable property: they deliver a complete, useful result without requiring account creation first. A recipe app Clip that shows the full recipe — then offers the full app for saved collections — converts at this rate. A Clip that shows the recipe title and then asks for sign-up to access the content does not. The unlock, not the promise of the unlock, is what earns the install.
App Store Search Clips and physical-surface Clips (QR, NFC, Maps) optimize differently. Search Clips arrive from users who typed a query, so the experience should answer the most common intent behind that query directly. Physical Clips arrive from users with established context — sitting at a restaurant table, attending an event — where intent is known before the Clip launches. Designing one experience to serve both surfaces produces an experience optimized for neither; separate invocation URLs with tailored experiences are the correct architecture for apps that have both channels.
App Clip card size limit: 10MB — and the 24-hour conversion window that makes timing critical
App Clips don't persist across device restarts, and Apple clears Clip data within 24 hours of last interaction. This privacy constraint is why the full-install conversion prompt must land inside the Clip session, not in a follow-up notification that will never arrive. The mechanism for this is SKOverlay: a system-provided install banner that slides up from the bottom of your Clip UI, showing your App Store icon and a "Download" button without navigating away from the Clip experience.
Timing the SKOverlay correctly is the variable that most determines whether Clip users install. Present it after a successful action — recipe loaded, parking confirmed, order submitted — not at launch. A user who just got value from your Clip is significantly more likely to install than one still figuring out what the Clip does. Track Clip-to-install conversion in the App Clips section of App Store Connect Analytics; it's reported as a separate acquisition source so you can isolate which invocation types are producing installs. The App Store Connect analytics guide covers how to read acquisition source data by cohort.
Physical touchpoints consistently outperform digital links for Clip conversion
Restaurant menus, product packaging, event badges, and venue check-in points generate the highest App Clip conversion because physical context establishes intent before the Clip launches. A QR code on a restaurant table pre-qualifies the user in a way App Store Search cannot: they're sitting at the table, they want to order, and a Clip that shows the menu and completes an order in under a minute converts that intent without an install barrier. The same pattern holds for museum exhibits, hotel room service, and brand packaging with functional digital extensions.
Maps integration is the underused physical-digital bridge: setting your Place Card action to open a Clip captures high-intent users at the moment of location lookup, before they've committed to visiting. A yoga studio Clip that shows today's class schedule and lets users book a spot directly from Maps is more useful at that moment than a link to the full app — and useful experiences convert. For apps with any physical presence, Maps-triggered Clips typically outperform Safari Smart App Banner Clips by a measurable margin.
When a Clip earns its build cost — and when it doesn't
An App Clip is worth building when your app satisfies three conditions: a single well-defined flow completable in under 60 seconds, a specific surface to link it to (App Store Search, a QR code, NFC tag, or Maps listing), and an iOS-first audience where these surfaces are meaningful acquisition channels. The build investment is typically 2–4 weeks — longer if your existing app wasn't architected with a separate Xcode target in mind. Without a specific surface and a focused flow, the cost rarely generates enough install volume to justify ongoing maintenance.
The categories where Clips consistently justify their cost include: subscription apps where a free-trial flow is the core conversion mechanic, ordering and commerce apps with physical locations, ticketing and event check-in apps, and parking or transit apps tied to specific locations. Apps where core value requires multiple sessions to demonstrate — fitness trackers, habit apps, productivity tools — rarely produce Clip conversion rates that make the investment worthwhile. Clips pair naturally with App Store In-App Events as complementary discovery surfaces: both give your app multiple impressions in App Store Search without additional paid acquisition spend.
Get your App Clip card assets right before building the experience
Your App Clip card in App Store Search shows the same icon as your main listing — a weak icon means a weak Clip card, and there's no separate asset to override it. Before investing weeks in Clip implementation, get your icon and screenshot assets into solid shape. For the full required dimensions across every iOS device class, the app icon size specifications cover every required export. Build your screenshot set — including assets that show the specific flow your Clip exposes — in the editor below.
Build your App Store assets in the editor →
Frequently asked questions
what is the app clip size limit
App Clips must be under 10MB after iOS system frameworks are deducted. The actual usable space for your code, assets, and libraries is closer to 3–6MB depending on your framework dependencies. This limit is enforced at submission time in App Store Connect — the binary is rejected if the Clip exceeds it, with no grace margin.
do app clips appear in app store search results
Yes — configuring an App Store Search experience URL in App Store Connect causes a Clip card to appear below your main listing in search results, labeled "Open." This gives your app two impressions from the same search query. The card uses a per-experience subtitle, separate from your main listing's subtitle field, so you can write copy specific to the Clip entry point.
how long does an app clip last before it expires
App Clips don't persist across device restarts. Apple clears App Clip data within 24 hours of the user's last interaction. After that, the Clip is gone and there is no re-engagement channel unless the user installed the full app. This is the intended privacy tradeoff that enables instant, permission-free launch — and it's why the SKOverlay in-session install prompt matters far more than any follow-up campaign.
how do i set up an app clip for app store 2026
Add an App Clip target to your Xcode project, then configure App Clip experiences in App Store Connect under your app's App Clips tab. Each experience links an invocation URL to a specific surface type: App Store Search, QR code, NFC, Maps, or Safari Smart App Banner. You can configure up to three advanced experiences (with custom images and per-experience subtitles) alongside an unlimited number of general experiences pointing to the same Clip binary.
do app clips improve app store search ranking
App Clips don't directly influence your app's keyword ranking — Clip metadata is indexed separately and doesn't feed the main App Store search index. However, full installs that originate from Clip sessions count as normal installs in Apple's conversion signals. A Clip driving consistent install volume from high-intent queries can contribute to install velocity, which is a secondary ranking signal. The primary ranking benefit is the second visible impression in search results, not a direct metadata effect.