- Selling an app means selling the business behind it: the code, the store listing and its users, the backend accounts and the revenue.
- Buyers price apps on profit after store fees and running costs, then adjust for retention, revenue model and platform risk.
- Check Apple's and Google's transfer rules before you agree a sale. Neither store moves the code; you hand it over yourself.
- Collect written assignments for code written by contractors, and remove secrets from the repository before any buyer sees it.
How do you sell an app?
Selling an app means selling the business behind it, not selling copies in a store. The buyer takes over the code, the App Store or Google Play listing with its users, ratings and reviews, the backend accounts, the domain and the revenue. Apple's documentation describes the moment plainly: "You'll need to transfer the ownership of an app when you've sold the app to another developer or you want to move it to another App Store Connect account or organization" (Apple).
If you want to charge for downloads on the App Store, that is a pricing choice, not a sale. This page covers how to sell a mobile app as a business, iOS, Android or both, to a stranger on a marketplace or to a company you know.
| Step | What you do | Why it matters |
|---|---|---|
| 1. Gather the numbers | 12 to 24 months of revenue, costs, users and retention | Buyers price apps on profit and trend |
| 2. Check that the app can transfer | Read Apple's and Google's transfer rules | Some apps need the whole developer account to move |
| 3. Confirm you own everything | Code, design, name, domain, and signed assignments from contractors | A buyer pays for clean ownership |
| 4. Choose where to sell | A marketplace listing, a broker, or a direct approach to likely buyers | Routes differ in fees, speed and reach |
| 5. Agree terms in writing | Price, what is included, escrow, handover help | Prevents disputes later |
| 6. Transfer and hand over | Store transfer, code, backend accounts and keys | The app keeps running for users |
Where can I sell my app?
There are four common routes. A developer who has sold several apps wrote on RevenueCat's blog: "In some cases buyers will reach out to you directly, but you'll most likely have to list your app for sale." He adds: "There are also companies that buy apps directly" (RevenueCat).
Marketplaces show your app to many buyers; brokers run a private sale for larger apps. Both charge fees, so get them in writing. The same developer warns that app brokers' "legal duties to you are limited to whatever is outlined in the listing agreement you signed" (RevenueCat).
A direct sale suits an app that fills a gap in someone else's product: a competitor, a company with the same users, or a platform your app plugs into. To sell an app to a company, send a one-page summary of what it does, who uses it and what it earns to the person who runs that product. Most app acquisition talks with larger companies start this way.
| Where to sell my app | Best for | What to watch |
|---|---|---|
| App and website marketplaces | Small and mid-size apps with a steady profit record | Listing and success fees; many buyers and many low offers |
| Brokers and M&A advisers | Larger apps, or app businesses with staff or several apps | Fees, minimum deal sizes and exclusivity in the listing agreement |
| Companies that buy apps directly | Apps in categories those companies already run | Quick offers that may sit at the low end |
| A company in your market | Apps that fit a buyer's product, users or platform | Longer talks; strategic fit can lift the price |
What do buyers look at when you sell your app?
Profit first: "take the gross revenue and subtract all expenses that directly contribute to generating that revenue", including store fees, servers, support and marketing (RevenueCat).
Then users, and how long they stay. Flippa, a marketplace, lists "Monthly Active Users (MAU), Customer Acquisition Cost (CAC), and Revenue Per User (RPU)" among the key numbers. FE International, a broker, adds that for mobile apps "where the curve flattens matters more than where it starts". Both are cited in the sources below.
The revenue model matters too: "Subscription apps with a history of low subscriber churn generally command much higher valuations than apps that are dependent on one-time purchases and/or ad revenue" (RevenueCat).
Platform risk is the last check. The buyer inherits Apple's and Google's rules, fees and review process, and an app that depends on one store or one traffic source is worth less.
| What buyers check | What they want to see | What lowers the price |
|---|---|---|
| Profit and trend | 12 months or more of steady or rising profit after all costs | Falling revenue, one-off spikes, unclear costs |
| Users | Monthly active users that hold up without heavy ad spend | Users bought with ads that stop when the ads stop |
| Retention | A cohort retention curve that flattens | A curve still falling months after install |
| Revenue model | Subscriptions with low churn | One-time purchases or ad revenue alone |
| Platform risk | More than one store or traffic source, current with store rules | One store, one ad network, outdated SDKs |
| Owner time | An app that runs on a few hours a week | An app that needs the founder every day |
How much is my app worth? App valuation multiples
App valuation multiplies profit by a figure that reflects how sure a buyer is that the profit will last after you leave. There is no official table, so note the basis and date of each published figure and treat them as ranges.
A developer guide on the RevenueCat blog says "apps typically sell for 12X - 36X the app's monthly profit" (RevenueCat). Flippa reported that in the first half of 2025 apps sold on its platform, above its minimum deal size, reached "an average annual profit multiple of 3.39x". FE International's 2026 transaction data puts subscription mobile apps with high retention at 3.5x to 6.0x adjusted earnings, and ad-supported and single-platform utility apps at 1.8x to 3.5x. The Flippa and FE International figures are cited in the sources below.
The figures come from different years, deal sizes and definitions of profit. An app with users but no profit is sometimes bought for its code, users or name, and no formula covers that.
If your app is a SaaS product with business customers, it is valued more like a software company: see SaaS valuation multiples. For the value of a business beyond the app, see what is my business worth.
| Published by | Multiple | Basis | Date |
|---|---|---|---|
| Developer guide, RevenueCat blog | 12x to 36x | Monthly profit | Published 2020, updated 2024 |
| Flippa (marketplace) | 3.39x average | Annual profit, apps above its minimum deal size | First half of 2025 |
| FE International (broker) | 3.5x to 6.0x | Adjusted earnings, subscription apps with high retention | 2026 |
| FE International (broker) | 1.8x to 3.5x | Adjusted earnings, ad-supported and single-platform utility apps | 2026 |
How do you transfer an app to a buyer on the App Store and Google Play?
On the App Store, the app moves between developer accounts and stays on sale. Apple says: "During and after the transfer, the app retains its reviews and ratings, and users continue to receive updates" (Apple). Before you agree a sale, check the criteria: "The app must have at least one version that was released to the App Store", "both parties must have accepted the latest version of their paid and free agreements", and "Apple Arcade apps can't be transferred" (Apple). If an app cannot meet them, "the only way to sell the app is to transfer the entire developer account to the buyer" (RevenueCat).
Apple moves the store record, not the code: "The transferor is responsible for exchanging the actual code set and building assets directly with the recipient." With Apple Pay, "the merchant ID isn't transferred along with the app", and with Sign in with Apple "you'll need to generate a transfer identifier for each user in your database" (Apple).
On Google Play, you send a transfer request and the receiving account approves it. Users, statistics, ratings, reviews and the store listing move. Reports stay behind: "Bulk export reports, payout reports, and earnings reports do not transfer with the app, so download any reports you need before starting the transfer." You need "the registration transaction ID for both the original account and the target account", and "After approval, support reviews and responds to transfer requests within two business days" (Play Console Help).
| Apple App Store | Google Play | |
|---|---|---|
| Who starts it | Your Account Holder starts it; the buyer's Account Holder accepts | You send a request; the receiving account owner approves |
| What moves | The app record, reviews and ratings; users keep getting updates | Users, download statistics, ratings, reviews and store listing |
| What stays behind | The code (you hand it over), the Apple Pay merchant ID, your App Analytics access | Bulk export, payout and earnings reports; orders made before the transfer |
| Before you start | At least one released version; both accounts with current agreements | Both accounts registered and active; transaction IDs for both |
| Extra steps | Subscriptions, Sign in with Apple, iCloud | Firebase, ad SDKs, signing keys |
To sell an iOS app and its Android version together, run both transfers. On Google Play, "Orders created before the app transfer remain in the original account" (Play Console Help).
Can you sell app source code on its own?
Yes, for example to a company that wants the product but not the users. To sell app source code you must own it. In the US, a copyright transfer "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" (17 U.S.C. 204). This is general information, not legal advice.
Code written by employees as part of their job usually belongs to the company: the Copyright Act treats "A work prepared by an employee within the scope of his or her employment" as a work made for hire (U.S. Copyright Office, Circular 30). Code written by freelancers and agencies is different. Without a signed assignment, the freelancer may still own it, so collect those assignments before you sell.
Open-source licenses in the code travel with it. Remove passwords, API keys and tokens from the repository and its history before anyone outside sees it; see remove secrets from git history.
What happens to your users and their data when you sell your app?
The users go with the app. On Google Play, "Google Play transfers all users, statistics, data, comments, ratings, subscriptions, and related app information to the target account" (Play Console Help). On the App Store, users keep receiving updates from the new owner.
The promises you made to those users go with them. When a large messaging app was acquired, the FTC wrote to both companies: "We want to make clear that, regardless of the acquisition, WhatsApp must continue to honor these promises to consumers" (FTC). For a small app, the buyer should keep to your privacy policy or ask users before changing how their data is used.
Show prospective buyers totals and charts, not user records. Transfer user data only at closing, under the purchase agreement.
Worked example: valuing a small subscription app (illustration)
This is an illustration written for this page, not a real app. Streakly is a fictional habit-tracker app on iOS and Android with a monthly subscription. Over the last 12 months it averaged $14,000 a month in revenue. Store fees in this example are 15%.
| Monthly average, last 12 months | Amount | Note |
|---|---|---|
| Revenue | $14,000 | Subscriptions on both stores |
| Store fees (15% in this example) | -$2,100 | Kept by the stores |
| Servers, tools and APIs | -$900 | Move to the buyer |
| Paid ads | -$2,400 | Needed to keep new users coming |
| Contract support and fixes | -$600 | Move to the buyer |
| Profit | $8,000 | $96,000 a year |
At 12x to 36x monthly profit, the developer-guide range, that is $96,000 to $288,000. At the 3.39x average annual profit multiple Flippa reported for apps in the first half of 2025, it is about $325,000. The gap is the point: published multiples give you a range to test offers against, not a price.
A retention curve that flattens and growth that does not depend on the $2,400 of monthly ads would lift Streakly within the range. Falling installs and contractor code with no signed assignment would push it down.
What if my app will not sell?
Many apps never find a buyer. Apple reviews old apps: developers with apps that "haven't been updated within the last three years and fail to meet a minimal download threshold" get a notice, and "you'll be asked to submit an update within 90 days". A removed app keeps working for people who have it: "Your app will remain fully functional for current users" (Apple).
Google closes inactive developer accounts: "Developer accounts that are inactive will be closed, and the registration fee will not be refunded." For an account with apps, the criteria include that all published apps "have less than 1,000 combined lifetime installs" and that the account "has not used Play Console in the last 180 days" (Play Console Help).
What remains: keep the app running at low cost, sell the code on its own, open-source it, or shut it down and delete user data as your privacy policy says. See open source the code or sell it, or, if the whole company is for sale, how to sell your startup.
Common mistakes when selling an app
Most app sales that fail break on the numbers, the ownership or the handover, not on the price.
- Valuing the app on revenue instead of profit after store fees, ads and running costs.
- Agreeing a sale before checking Apple's and Google's transfer rules.
- Handing over the store listing without the code, keys and backend accounts the buyer needs to ship an update.
- Selling code written by freelancers who never signed an assignment.
- Sharing source code or user records with a prospective buyer before a confidentiality agreement and a signed deal.
- Taking the first offer. A developer who has sold several apps warns that "the first offer you get will likely undervalue your app" (RevenueCat).
Are an app's code and records also a data asset?
Sometimes, and separately from the sale of the app. AI data buyers have asked Origin for codebases with their full commit history, reviews and issue history, from software companies that are operating, being sold or closing; for SaaS companies, the product's usage and support history alongside the code. For an app, that is the repository with its history, reviews and issues.
What must come out first: secrets and credentials, customer data and personal data, third-party and open-source code the company does not own outright, and anything an acquirer or investor has rights over. For a consumer app, records about identifiable users stay out. If you have sold the app or are about to, the purchase agreement decides who owns the code and records, and whether you keep a copy. See SaaS database and warehouse records and remove secrets from git history.
Origin is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
How do I sell my app?
Gather 12 to 24 months of revenue, costs, downloads and retention. Check that the app meets Apple's and Google's transfer rules. Confirm you own the code, name and domain, with signed assignments from any contractors. Then list it on a marketplace, hire a broker or approach likely buyers directly. Agree the price and what is included in writing, use escrow, and finish with the store transfer and the code handover.
Where is the best place to sell my app?
It depends on the app. App and website marketplaces reach many buyers and suit small apps with steady profit. Brokers run a private sale for larger apps. Some companies buy apps directly and make quick offers. A direct sale to a company in your market, such as a competitor or a platform your app plugs into, takes longer but can pay more for a good fit.
How much is my app worth?
Most apps are priced as a multiple of profit after store fees and running costs. A developer guide on the RevenueCat blog puts typical sales at 12 to 36 times monthly profit, and Flippa reported an average of 3.39 times annual profit for apps sold on its platform in the first half of 2025. Low churn, steady growth and little owner time push the multiple up.
Can I sell my app's source code without selling the app?
Yes, if you own it. A US copyright transfer must be in writing and signed by the owner, and code written by freelancers may still belong to them unless they signed an assignment. Check the open-source licenses in the code, remove passwords and API keys from the repository history, and set out in writing who may use the code and whether you keep a copy.
Can I transfer an iPhone app to a buyer's Apple developer account?
Usually, yes. Apple's app transfer moves the app to the buyer's account while it stays on the App Store with its ratings and reviews. The app must have at least one released version, both accounts must have accepted current agreements, and Apple Arcade apps cannot move. Apple does not move the code; you hand it over. Apple Pay and Sign in with Apple need extra steps.
How do I transfer an Android app to a buyer on Google Play?
Both developer accounts must be registered and active, and you need the registration transaction ID for each. You send a transfer request and the buyer's account approves it. Google moves the users, statistics, ratings, reviews and store listing. Download your payout and earnings reports first, because they stay behind. After approval, Google says support responds within two business days.
How do I sell an app to a company?
Pick companies for which your app fills a gap: a competitor, a company that sells to the same users, or a platform your app plugs into. Send a one-page summary of what the app does, who uses it and what it earns to the person who runs that product. Sign a confidentiality agreement before you share details, and get any offer in writing.
What happens to my app's users and their data when I sell the app?
The users move with the app. Google Play transfers users, statistics, data and subscriptions to the buyer's account, and on the App Store users keep receiving updates. The promises in your privacy policy move too, so the buyer should keep to them or ask users before changing how their data is used. Share totals, not user records, with buyers before closing.
What can I do if nobody wants to buy my app?
Keep it running at low cost, sell the code on its own, open-source it, or shut it down and delete user data as your privacy policy says. Watch the store rules: Apple may remove apps that have not been updated in three years and get very few downloads, and Google closes inactive developer accounts without refunding the registration fee.
Sources and further reading
- Apple Developer: Overview of app transfer (App Store Connect Help)
- Apple Developer: App transfer criteria (App Store Connect Help)
- Play Console Help: Transfer apps to a different developer account
- RevenueCat blog: How to sell your mobile app (published 2020, updated 2024)
- Flippa: Online business trends and data insights (H1 2025 multiples)
- Flippa: Mobile app valuation and multiples in 2025
- FE International: Marketplace app valuations in 2026
- Cornell LII: 17 U.S. Code 204, Execution of transfers of copyright ownership
- U.S. Copyright Office: Circular 30, Works Made for Hire
- FTC Bureau of Consumer Protection: letter on WhatsApp privacy promises in an acquisition (2014)
- Apple Developer: App Store Improvements
- Play Console Help: Closure of inactive developer accounts
