Key takeaways
- Framer hosts websites and has no app or HTML export. An iOS app is always a native shell around your live Framer site, published in your own Apple Developer account.
- Framer recommends itself for marketing sites, and Apple rejects marketing material as apps under 4.2.2. Only Framer projects people return to – a publication, catalog, members' library or venue – should become apps.
- On the Framer side you need a paid plan with a custom domain, Pro for well-known files and universal links, and a calmer animation setup in app mode.
- WebViewGold, built by our team, adds push, offline pages, universal links and Sign in with Apple support; appsubmitter.io handles signing, the listing and App Review.
Our recommended solution
Turn your Framer app into a real iOS app with WebViewGold
WebViewGold wraps the Framer web app you already have in a native Xcode project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at the App Store look for. Built by our own team, and we submit WebViewGold apps all the time.
Framer to App Store: is it possible, and what does it take?
Yes, you can convert Framer to an iOS app – but the app is something you build around Framer, not something Framer exports. Framer publishes and hosts websites; as of October 2026 there is no app export, and Framer "does not offer HTML export for self-hosting" either. What works is a native app around your live Framer site: it adds device features the browser lacks and goes out through your own Apple Developer account.
Whether Apple accepts that app is a separate question. Guideline 4.2 sets the bar: "If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store." Framer's own positioning shows the tension: its comparison page recommends Framer for "Brand, campaign, editorial, and product-marketing sites" and points to Lovable for builds that need accounts, transactional data or payment flows (Framer). A brand site in an app shell is marketing material – exactly what Guideline 4.2.2 doesn't want an app to be.
So this guide starts with the decision and only then gets to Xcode. If your Framer project passes the test below, the rest is a well-trodden path.
Should your Framer site be an app? Five questions to answer first
- Do people return on their own? A magazine, a members' library or a venue program gets weekly visits; a portfolio or a launch page gets one.
- Is there news people would opt in to? New episodes, schedule changes, fresh member content – not "we shipped a new feature".
- Would offline access help? A festival map, a menu, a course handout, a field guide.
- Is there a signed-in area? A members' area run through a plugin such as Outseta benefits from Face ID re-login and push for new content.
- Is the content the product? If every page exists to send visitors to a sign-up or a product somewhere else, the app would be an advertisement.
Three or more honest "yes" answers make your Framer project a candidate. With fewer, the better options lie elsewhere: keep improving the website, offer a home-screen web app through a third-party service such as Progressier – which has a Framer integration but notes that a service worker can't be added to a Framer site – or build the real app part with a tool designed for applications and keep Framer for marketing.
Want your Framer app in the App Store without the trial and error?
Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.
Three ways to get Framer content onto iPhones
| Criterion | Wrap the Framer site (WebViewGold) | Split: Framer for marketing, app built elsewhere | Home-screen web app |
|---|---|---|---|
| What users get | Your Framer content plus native push, offline pages and universal links | A dedicated app – native, Capacitor or an app builder – with its own features | Your site in its own window; web push on iOS 16.4 and later |
| App Store listing | Yes | Yes | No |
| Content workflow | Unchanged: edit and publish in Framer | Two products to maintain | Unchanged |
| Main risk | Guideline 4.2 if the native layer stays thin | Time and budget | Limited device integration and no offline support through a service worker |
| Best for | Publications, catalogs, members' libraries, venues | Products that need accounts, data and payments | Light use cases without App Store plans |
Capacitor isn't a separate route for a Framer site. Without an HTML export there is nothing to bundle, so it could only load your remote site through server.url – a setting Capacitor's configuration reference describes as intended for live-reload servers and "not intended for use in production". You would end up with a wrapper minus the ready-made native modules.
Prepare the Framer project: domain, plan and settings
| Setting | Where you find it | Why the app needs it |
|---|---|---|
| Custom domain | The Domains section of your site settings; requires a paid plan | A permanent start URL instead of the auto-generated framer.app address |
| "Made in Framer" badge | Disappears once a custom domain or paid plan is active – after you republish | A badge that links to Framer makes the app look like a website |
| Well-known files | Site settings or Static Files, on Pro plans and above | Hosts apple-app-site-association for universal links |
| Staging | The Staging tab, on Pro plans with staging enabled | Lets you prepare changes while a build is in review |
| Custom code | Framer's custom code settings for head or body | Holds the snippet that switches the site into app mode |
| CMS collections | The CMS panel | The source of everything worth a push notification |
Outside Framer, you need to be enrolled in the Apple Developer Program (as an individual or an organization), Xcode on a Mac or the separately sold WebViewGold Cloud Builder, and privacy policy and support pages on your site for App Store Connect.
Calm the site down: an app mode for Framer pages
Framer sites are often built to impress on a big screen – parallax, scroll-triggered reveals, video backgrounds, cursor effects. On a phone, inside an app, the same effects delay the first screen, cost battery and can stutter in a WebView on older iPhones. A calmer version meets Apple's design expectations and a reviewer's patience more easily – see Guideline 4.0 for WebView apps.
- Detect the app. WebViewGold can send a custom user agent, and a short script in your custom code adds a marker class when it sees it.
- Reduce motion in app mode: switch off parallax and scroll animations, replace video backgrounds with stills, keep transitions short.
- Hide web furniture: the site's top navigation if the app provides its own, the cookie bar, waitlist pop-ups, "book a demo" banners and any store badges – a Google Play badge can trigger Guideline 2.3.10.
- Route external links out: scheduling tools, embedded forms from other services and social profiles open outside the app.
- Check sticky elements against the notch and the home indicator inside the app, not just in a browser.
One rule keeps you clear of Guideline 5.6: app mode changes how things look and move, never which features exist.
The shortcut from Framer to the App Store
WebViewGold: your Framer app, native on iOS
Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:
- Push notificationsOneSignal or Firebase, for real, personal events
- Native offline screenNo browser error pages when the connection drops
- Native splash screenApp-like start instead of a loading web page
- Deep linksLinks open the right screen inside the app
- QR & barcode scannerDevice features the website alone can't offer
- In-app purchasesNative purchase flows where the store requires them
No tool guarantees an approval: Apple still judges what your app offers. Use the native features in your main user journey – our App Specialists review your WebViewGold app before it goes to the App Store.
Convert Framer to an iOS app with WebViewGold, step by step
WebViewGold, made by our team, is a ready-made Xcode project in Swift that turns any site running in Safari into a native app. It's a one-time purchase, the project belongs to you, and selling In-App Purchases requires the Extended license. For a Framer site:
- Enter the custom domain in
Config.swiftand confirm the start page loads without a redirect. - Connect push through OneSignal, Firebase or Pushwoosh and decide which CMS events deserve a message – a new issue, a schedule change, new member content.
- Bundle offline pages. Framer content lives only on Framer's servers, so put the pages people need without signal – a program, a menu, a map – into the local HTML bundle and let the native offline screen cover the rest.
- Turn on universal links: add your domain under Associated Domains in Xcode and make sure the
apple-app-site-associationfile among your Framer well-known files lists the app. - Add device features with a purpose: a QR scanner for tickets or loyalty codes at a venue, Face ID for the members' area, the native share dialog for articles, Apple's rating dialog.
- Use the Sign in with Apple helper if your member tool supports Apple sign-in – WebViewGold recognizes Apple's sign-in page automatically.
- Add the finishing touches – icon, splash screen, pull-to-refresh, dark mode – and test the build through TestFlight on an iPhone and an iPad.
No Mac at hand? Use the Cloud Builder, which works entirely in the browser, or let our team handle the setup.
Members, payments and privacy when Framer relies on plugins
Sign-in
Framer has no built-in user accounts, so logins come from plugins such as Outseta, which offers email and password or Google. Email and password work inside the app. Google's sign-in pages refuse to load in an embedded web view (disallowed_useragent), so choose one of these, in this order:
- Build Google login natively – Google's iOS Sign-In SDK or an
ASWebAuthenticationSessionflow. That is custom code in the Xcode project, which you can also have quoted as a customization. - Offer email and password in the app – plus Sign in with Apple if your member tool supports it – and keep Google on the website. Members who joined with Google then need a way to set a password.
- Handing the login to Safari is the fallback of last resort. Google accepts it, yet Apple considers linking out to the browser to sign in a poor experience under Guideline 4.
If Google remains an in-app route to the main account, Guideline 4.8 requires an equivalent login that limits data to name and email and lets people hide their address – Sign in with Apple qualifies. Accounts created in the app also need in-app deletion under Guideline 5.1.1(v).
Payments
Framer has no native payments; plugins such as Outseta or StripeKit connect Stripe. Memberships, courses and downloads unlock digital content, so the iOS app generally has to sell them through In-App Purchase (Guideline 3.1.1) – our 3.1.1 guide covers the exceptions. Tickets, table reservations and merchandise are consumed outside the app, and Guideline 3.1.3(e) requires other payment methods for them, so your Stripe checkout can stay.
Privacy
Declare what the app collects through the site in your App Privacy details: Framer form submissions, member data in your plugin and any analytics or marketing scripts you added. If anything tracks people across apps and websites, App Tracking Transparency applies.
Where Framer apps stumble in review – and where appsubmitter.io helps
- 4.2 Minimum Functionality: a brand site with a splash screen. Fix the purpose first – see 4.2 for WebView apps.
- 5.6 Developer Code of Conduct: republishing during review, a switch from framer.app to your domain, claims the app doesn't keep – see Framer apps and Guideline 5.6.
- 2.1 App Completeness: protected pages without a demo account, broken embedded forms.
- 4.8, 3.1.1 and 5.1.1(v): Google login without an equivalent, web checkouts for digital access, sign-up without deletion.
In the Notes for Review, say plainly that the app displays your Framer website on your own domain, describe every native feature together with the steps to test it, and add a demo account. Screenshots should show app screens – CMS content, the offline page, a notification – rather than your hero section.
appsubmitter.io takes the submission off your hands: code signing and an automated build pipeline set up in your own Apple Developer account, the App Store listing and App Privacy details, AI-powered pre-submission checks reviewed by an App Specialist, and the communication with App Review. Changes to your site or code aren't part of the package but are quoted upfront, and your app doesn't need to be finished when you book. Book the iOS service or start with a free consultation call. Planning Google Play too? Read how to convert Framer to an Android app.
Checklist before you submit
- Your Framer project passes the five-question test – people have their own reasons to return to it.
- A paid plan with custom domain is active, and the site was republished so the "Made in Framer" badge is gone.
- apple-app-site-association is uploaded as a well-known file (Pro or higher) and matches the app's Associated Domains.
- Parallax, video backgrounds and heavy animations are reduced in app mode and tested on an older iPhone.
- App mode hides site navigation, cookie bar, waitlist forms and store badges – presentation only.
- Push notifications are tied to new CMS items or events people opted into.
- Offline, the app shows a native screen and locally bundled key pages.
- Members sign in with email and password inside the app; Google login runs natively or stays on the website.
- Digital memberships sold in the app use In-App Purchase, and account deletion is available in the app.
- The review notes name every feature with test steps and include a working demo account.
Frequently asked questions
Can I convert Framer to an iOS app without writing code?
Does Framer have an app export or a native mobile option?
Do I need a Mac to publish a Framer site as an iPhone app?
Can I use Capacitor instead of a wrapper for my Framer site?
server.url at the live site, which Capacitor's documentation says is not intended for production. At that point you have a wrapper without ready-made native modules, so WebViewGold or a native rebuild is the more sensible choice.Will my Framer animations work inside the app?
How long does App Store review take for a Framer app?
Can I change the app later by republishing in Framer?
Recommended solution
From Framer to the App Store: WebViewGold + appsubmitter.io
- 1 Build with WebViewGold Turn your website into native iOS and Android projects.
- 2 Add native value Push, offline screen, deep links or scanning in your main flow.
- 3 We submit it Our App Specialists submit and talk to the review team.
WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.
Sources and further reading
- Apple – App Store Review Guidelines, 4.2 Minimum Functionality
- Apple Developer – Offering account deletion in your app (sign-in via the default browser)
- Framer Help – Can I export my website to HTML and self-host it?
- Framer – Framer vs. Lovable comparison
- Framer Help – Well-known files
- Framer Marketplace – Outseta plugin (login, memberships, Stripe)
- Progressier – PWA integration for Framer
- Capacitor – Configuration reference (server.url)
Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.