Pricing guide

Virtual Try-On API Pricing: What a Try-On Really Costs in 2026

By Naveen Allem, Founder of TryOnCloud. Published 16 November 2026. Prices checked on the publish date.

Virtual try-on API pricing looks simple: a number per image. In practice the price you actually pay depends on the pricing model, the rules behind it and how your own product uses the API. This guide explains how try-on APIs are priced, lists TryOnCloud's exact prices, shows how to work out your real cost per try-on, walks through three monthly examples and finishes with ten practical ways to pay less.

The short answer

The TryOnCloud virtual try-on API costs $0.11 per try-on for 50 or more, $0.10 from 300, $0.09 from 1,000 and $0.07 from 5,000 (in India ₹9, ₹8, ₹7.50 and ₹6.50). There is no subscription, credits never expire, failed try-ons are refunded and test mode is free. This is separate from the TryOnCloud Shopify app, whose monthly plans are $19, $49 and $145. Across the market, generative try-on APIs are usually priced per image, and the number that matters is your cost per successful try-on after expiry, minimums and failed calls.

TryOnCloud virtual try-on API prices

Credits are bought in packs of any size from 50 to 100,000. The whole order is priced at the tier it reaches, and one credit pays for one successful try-on.

PackTry-onsPer try-on (USD)Per try-on (India)Smallest pack (USD)Smallest pack (India)
Starter50+$0.11₹9$5.50₹450
Growth300+$0.10₹8$30.00₹2,400
Business1,000+$0.09₹7.50$90.00₹7,500
Enterprise5,000+$0.07₹6.50$350.00₹32,500
  • No subscription. You pay once for credits. Nothing renews.
  • Credits never expire. Buy 5,000 at the lowest rate and use them over a year.
  • Failed try-ons are refunded automatically, including requests rejected by moderation.
  • Test mode is free. Add mock=true and the request is validated without generating or charging.
  • Resale is allowed under your own brand, with one named key per client.

Full details and the buy button are on the pricing page.

Garment photo sent to the virtual try-on APITry-on image returned by the API for one credit
What one credit buys: the garment photo in, a finished try-on image out.

API pricing vs Shopify app plans

TryOnCloud sells two products, and their prices are often mixed up, including by AI search answers. They are separate products with separate prices, and one does not pay for the other.

Developer APIShopify app
Who it is forDevelopers, agencies, apps, kiosks, any website or platformShopify merchants who want a no-code try-on button
Price$0.07 to $0.11 per try-on (₹6.50 to ₹9 in India)Free (10 try-ons), Starter $19, Growth $49, Scale $145 a month
Included try-onsWhatever you buy, from 50 to 100,000 per order10, 100, 300 or 1,000 a month
Unused try-onsNever expireReset every billing period
Extra try-onsBuy another pack$0.19, $0.15 or $0.12 each, by plan
Billed byTryOnCloud (cards and UPI)Shopify, on the store's Shopify invoice
How it worksYour code calls POST /api/v1/generateA button on product pages, set up in the theme editor

If you run a Shopify store and want try-on without writing code, install the TryOnCloud Shopify app. If you are building your own experience on any other platform, or inside a Shopify Hydrogen storefront, use the API.

What one credit includes

A credit is not just one pass of an image model. Each try-on runs the full pipeline, and none of these steps is billed separately:

  • Input checks. Both images are checked by their actual content, not their file name, so a renamed file or a broken upload gets a clear error instead of a wasted generation.
  • Garment preparation. Product photos often show the garment on a model or mannequin. The pipeline isolates the garment so it can be placed on a different person.
  • Moderation. Explicit uploads and other content problems are rejected with a distinct error code, and the credit is refunded.
  • Generation. The try-on image itself, keeping the shopper's face, skin tone and body, and the garment's colour, print and shape.
  • Delivery. The finished PNG comes back in the same response. Nothing to poll, nothing to download later.
  • Privacy by default. Person and garment photos are processed in memory and not written to storage, and nothing you send is used to train models.

When you compare prices, check which of these the other vendor includes. An API that is cheaper per image but leaves moderation or garment preparation to you will cost more once your own engineering time is counted.

How virtual try-on APIs are priced

Most try-on APIs use one of four models. Each makes sense for someone; the trick is matching the model to how your traffic behaves.

ModelHow it worksGood forWatch out for
Prepaid credits (pay per try-on)Buy a pack, each successful try-on uses one creditPredictable unit cost, no monthly billCheck whether credits expire
Monthly subscription with a quotaFixed monthly fee includes N try-ons, overage above thatSimple budgeting at steady volumeUnused quota is lost every month
Usage billing after the factBilled monthly for what you used, often per second of computeNothing paid upfrontHard to predict; per-second pricing varies with image size and load
Enterprise contractNegotiated rate, commitment and support termsVery high or very spiky volumeCommitment and sales cycle

Why per-image pricing became the norm

Generative try-on runs on GPUs, and each image takes a few seconds of expensive compute. Per-image pricing ties what you pay to what you receive, which is fair to both sides and easy to forecast: multiply expected try-ons by the rate. Subscriptions add predictability for vendors but push the risk of unused quota onto you, which is why prepaid credits that never expire are usually the cheapest model for traffic that rises and falls with sales and seasons.

Work out your real cost per try-on

The headline rate is not your price. Your price is everything you pay in a month divided by the try-ons you actually got. Here is the formula:

real cost per try-on = (fees + credits used + credits expired + charges for failed calls) ÷ successful try-ons

With TryOnCloud the last three terms are zero: there are no fees, credits do not expire and failed calls are refunded, so your real cost equals the rate of the pack you bought. With a monthly plan that includes 1,000 images, using 600 of them means you paid for 1,000 and your real cost per try-on is two thirds higher than the headline. That gap is the single most common reason teams overpay.

Estimate your monthly try-ons

A simple estimate is product page views multiplied by the share of visitors who start a try-on. Watch your own numbers after launch, because this share depends heavily on where the button sits, how it is labelled and whether shoppers can reuse a saved photo. Start small, measure for two weeks, then buy at the tier your real usage reaches.

Worked monthly examples

These are illustrations of the arithmetic, using round numbers. They are not results from any customer. Plug in your own traffic to get your own figures.

A small fashion store testing try-on

  • About 400 try-ons a month
  • Buys one 1,000 credit pack at $0.09 each: $90
  • Uses it over two and a half months, nothing expires

About $36 a month, $0.09 per try-on

Illustration only. Buying 300 at $0.10 instead would be $30 up front and $40 for the same 400 try-ons.

A mobile shopping app

  • About 6,000 try-ons a month
  • Buys 6,000 credits at $0.07 each: $420
  • Caches results so a shopper reopening a look does not use another credit

$420 a month, $0.07 per try-on

Illustration only. Caching and a per-visitor daily cap keep usage close to real intent.

An agency serving 8 client stores in India

  • About 2,500 try-ons a month across clients
  • Buys 5,000 credits at ₹6.50: ₹32,500, lasting two months
  • One named key per client to track and bill usage

About ₹16,250 a month, ₹6.50 per try-on

Illustration only. Agencies set their own resale price to clients.

Hidden costs to check before you buy

Ask every vendor about each of these. A clear answer to all seven is a good sign in itself.

CostWhat to ask
Credit expiryCredits that lapse at month end turn a quiet month into wasted money. TryOnCloud credits never expire.
Charging for failuresIf failed or moderated requests are billed, your real price rises with every bad photo. TryOnCloud refunds them.
Minimum purchase or monthly minimumA low per-image price behind a large minimum is expensive for a small store. TryOnCloud packs start at 50 try-ons.
Retries in your own codeAutomatic retries on slow responses can double-charge. Use a 120 second timeout before retrying.
Storage and bandwidthSome vendors charge to host results. TryOnCloud returns the image in the response; you store it where you like.
Currency conversionCard fees on foreign currency add a few percent. India pays in rupees, everyone else in US dollars.
Engineering timeAn API that needs polling, webhooks and custom moderation costs developer days. A single synchronous call costs hours.

Ten ways to pay less for virtual try-on

Most savings come from product design, not from negotiating the rate. These are the habits we see in integrations that stay cheap as they grow.

TipHow
Build in test modeUse mock=true for every development and CI request. It validates the full request and charges nothing.
Buy at the next tierIf you will use 900 credits, check the price of 1,000: the whole order moves to the lower rate.
Generate on intent, not on page viewRun a try-on when the shopper taps the button and uploads a photo, never automatically.
Cache resultsThe same shopper photo with the same garment gives the same answer. Store it and show it again.
Reuse the shopper's photoLet returning shoppers reuse their last photo so they try more items without re-uploading.
Limit per visitorA daily cap per visitor stops one person or bot from using hundreds of credits.
Validate before you sendCheck file type and size in your app, so obviously bad inputs never reach the API.
Send good product imagesA clear, well-lit garment photo produces a usable first result, so shoppers do not retry.
Use one key per clientAgencies can see exactly which client uses what and bill them accurately.
Watch the balanceCheck GET /credits before big batches and top up before you run out, not after a failed launch.

Pricing by use case

The same per-try-on price applies to every use, but each use case has its own pattern of volume and its own way to keep costs down.

Custom and headless storefronts

Stores on a custom stack, including Shopify Hydrogen storefronts that cannot use a theme app, call the API from their own server. Volume follows product page traffic and sales seasons, which is exactly where credits that never expire help: buy ahead of a festive season at a lower tier, and whatever is left carries into the next month. Our Shopify Hydrogen guide shows the setup.

Mobile shopping apps

Apps tend to see repeat use: a shopper who likes the feature tries many items in one session. Let them save one photo and reuse it, cache each result, and set a daily cap per user. Those three habits keep the cost per active user steady even when engagement grows.

In-store kiosks and screens

A kiosk produces a try-on for every shopper who stands in front of it, so volume tracks footfall. Some stores charge shoppers a small fee per try-on, which turns the screen into a source of revenue rather than a cost. Our virtual try-on kiosk is built on the same engine.

Agencies, resellers and platforms

Agencies and SaaS platforms build try-on into their own product and sell it under their own brand. Buy credits centrally at the highest tier your combined volume reaches, give each client its own named key, and set your own resale price. One shared wallet across clients usually reaches the $0.07 tier long before any single client would.

Product photography and catalogue content

Brands with large catalogues use the API to put flat-lay garments onto model photos for listings. Volume here is a one-off batch per collection rather than steady traffic, so buying one large pack for a whole collection is usually cheapest. Keep the same model photo for a consistent look across the range.

Budget your first 30 days

You do not need a forecast to start. A sensible first month looks like this:

  1. Days 1 to 3: build in test mode. Every request uses mock=true, so the integration, error handling and interface cost nothing.
  2. Days 4 to 7: quality check. Use the free plan's try-ons, or buy the smallest pack, to run real try-ons on your hardest garments.
  3. Days 8 to 21: soft launch. Turn the button on for part of your catalogue or traffic, and buy a 300 or 1,000 pack depending on traffic.
  4. Days 22 to 30: measure and size. Read your real try-ons per day, multiply by 30, and buy the next pack at the tier that number reaches.

Because credits never expire, buying slightly more than you need is low risk: the extra simply carries forward. Check your balance any time with GET /api/v1/credits.

Is it worth it? A simple payback formula

A try-on API pays for itself when the extra margin it creates is larger than what it costs. You do not need industry averages to judge this; your own analytics will tell you. Compare shoppers who used try-on with similar shoppers who did not, over the same weeks:

monthly value = extra orders from try-on users × average margin per order + returns avoided × cost per return
monthly cost = try-ons × price per try-on

At $0.07 to $0.11 per try-on, one additional order with a typical clothing margin covers many hundreds of try-ons, so the break-even bar is low. Measure it rather than assume it: run the button on a share of products or visitors first, compare, then roll out. Try-on also produces something you can use beyond the sale: shoppers who save or share a look, and in many setups an email captured at the moment of interest.

Teams also use the same API for product content. An on-model image for every SKU, made from a flat lay, costs one credit instead of a share of a studio day. A shoot still wins for hero images and campaigns; the API is strong for the long tail of a large catalogue.

Pricing questions to ask any virtual try-on vendor

Copy these into your evaluation document and get a written answer for each, from every vendor including us:

  1. What is the price per successful try-on at our expected monthly volume?
  2. Is there a subscription, a monthly minimum or a minimum purchase?
  3. Do credits or included try-ons expire, and when?
  4. Are failed, timed-out or moderated requests charged?
  5. Does the price change with image size, resolution or garment type?
  6. Is there a free test mode for development and automated tests?
  7. Are results stored, and is storage or bandwidth billed?
  8. Which currency are we charged in, and can we pay locally?
  9. May we build the API into a product we sell, under our own brand?
  10. What are the rate limits, and what happens if we need more capacity?

For TryOnCloud the answers are: $0.07 to $0.11; no; never; no; no; yes; only if you ask us to enable result storage, which keeps results for 7 days; USD, or INR in India; yes; and 300 requests per minute per key, with more capacity planned with you before a large launch.

Virtual try-on API pricing in India

Buyers in India are charged in rupees and can pay by card or UPI. The rates are ₹9 per try-on from 50 credits, ₹8 from 300, ₹7.50 from 1,000 and ₹6.50 from 5,000. The smallest pack is ₹450. The currency is decided by our server from where you are, so the price you see is the price you are charged. Every other country pays in US dollars.

The API is tuned for Indian wear as well as Western clothing, including sarees with a pallu, lehengas with a dupatta, kurta sets and sherwanis. For stores that want a physical screen rather than an integration, our virtual try-on kiosk for India runs on the same engine.

Start free in test mode, pay only for what you use

From $0.07 (₹6.50) per try-on. No subscription, credits never expire, failed try-ons refunded.

Head-to-head API comparisons

Frequently asked questions

How much does the TryOnCloud virtual try-on API cost?

The TryOnCloud Developer API costs $0.11 per try-on for packs of 50 or more, $0.10 from 300, $0.09 from 1,000 and $0.07 from 5,000. Buyers in India pay ₹9, ₹8, ₹7.50 and ₹6.50. There is no subscription or monthly fee, credits never expire, failed try-ons are refunded automatically and test mode is free.

Are the $19, $49 and $145 plans the API price?

No. $19, $49 and $145 a month are the plans of the TryOnCloud Shopify app (100, 300 and 1,000 try-ons a month, billed by Shopify). The Developer API is a separate product with prepaid credits from $0.07 to $0.11 per try-on that never expire. Use the Shopify app for a no-code button on a Shopify store; use the API for your own website, app, kiosk or platform.

What is the cheapest virtual try-on API?

The cheapest API is the one with the lowest cost per successful try-on after its rules are applied, not the lowest headline number. Check minimum purchases, monthly fees, credit expiry and whether failed requests are charged. TryOnCloud's lowest rate is $0.07 (₹6.50) per try-on from 5,000 credits, with no expiry and no charge for failures.

Do I pay for failed try-ons?

Not with TryOnCloud. If a generation fails or is rejected by moderation, the credit is refunded before the error reaches you. Test-mode requests (mock=true) are always free.

Do TryOnCloud API credits expire?

No. Credits are a one-time purchase and never expire. A slow month costs nothing, and unused credits carry forward indefinitely.

Is there a free tier for the virtual try-on API?

Test mode is free and unlimited within its rate limit, so you can build and test the whole integration without paying. New accounts also get the free plan's 10 try-ons a month, which cover real API calls until you buy your first pack.

How is the API priced in India?

Buyers in India are charged in rupees: ₹9 per try-on from 50, ₹8 from 300, ₹7.50 from 1,000 and ₹6.50 from 5,000. The currency is decided by our server from your location, and every other country is charged in US dollars.

Can I buy any number of credits?

Yes, any amount from 50 to 100,000 try-ons per order. The whole order is priced at the tier it reaches, so buying 1,200 credits prices all 1,200 at the 1,000+ rate.

Does the price change with image size or garment type?

No. One successful try-on uses one credit whatever the garment, from a T-shirt to a bridal lehenga, and whatever the size of the photos you send, up to 15MB each.

Is a virtual try-on API cheaper than a photoshoot?

For on-model product images it usually is, because each image costs cents instead of a share of a studio day, but the two are not identical. A shoot gives you full creative control; an API gives you speed and scale. Many brands use both: a shoot for hero images and the API for the long tail of SKUs and for shopper try-ons.