Looking for a free background removal API? See what remove.bg, Photoroom and Bria give you before billing starts, what each costs per image from 1,000 to 100,000 photos, and when self-hosting rembg is cheaper. Includes the model license trap, a 20 image test plan, and a free browser tool for manual cutouts.
You searched for a free background removal API, so the real question is how many images you can cut out before a card gets charged. In October 2026 the honest answer is: fewer than you would like. remove.bg gives you 50 API previews a month, Photoroom gives you 10 clean production calls, Bria gives you 100 trial calls, and the only unlimited route is running open source software on hardware you pay for yourself.
This article puts the real numbers side by side, shows the catch behind each free tier, and prices what happens when you outgrow it. Every figure comes from the vendor's own pricing or documentation page, or from fal's published roundup where noted. Prices move, so check the date before you commit a budget.
💡 Short version: prototype on a free tier, run a 20 image test on your hardest photos, then choose between a pay-per-image API and a self-hosted model based on your monthly volume.
Nobody gives away GPU time forever. In the image background remover market, "free" means one of three things, and mixing them up is how a weekend project turns into a surprise invoice:
A free tier renews. A free trial is a fixed pile of calls. remove.bg's 50 monthly previews are a tier. Bria's 100 calls are a trial. Photoroom sits in between: sandbox calls are free and renew, but the output is watermarked, while its 10 clean production calls are a one-time starter.
The difference matters for planning. A tier can support a hobby site that processes 40 photos a month. A trial can only support testing, and you should spend it on your ugliest images, not your prettiest ones.
Open source tools like rembg cost nothing to download, yet every cutout still burns CPU or GPU time somewhere. On your laptop that time is free. On a cloud server it becomes a monthly bill, and on a busy shop it becomes an engineer's afternoon spent keeping the service alive. Free describes the license, not the total cost.
Here is what each option hands over before billing starts, and the limit that makes it a test rather than a production plan.
| Provider | Free allowance | The catch |
|---|---|---|
| remove.bg API | 50 previews per month | Previews are limited to 0.25 megapixels |
| Photoroom Remove Background API | 10 clean production calls, plus sandbox mode | Sandbox results carry a watermark |
| Bria API | 100 free calls on the Trial plan | One-time allowance, then $0.018 per image |
| rembg, self-hosted | Unlimited | You supply the hardware, and the default model needs a commercial agreement |
| Remove Background on PicassoIA | Described as free and online on its model page | A web tool, not a developer API endpoint |
remove.bg's API page states that "your first 50 API calls per month are on us," and the company's help page explains that these are previews of up to 0.25 megapixels, roughly 500 by 500 pixels. That is enough to prove the integration works and to judge edges at a glance. It is not enough to ship a catalog.
Paid output goes much higher: PNG up to 10 megapixels, and JPG, WebP or ZIP up to 50 megapixels. The rate limit is generous at up to 500 images per minute, but it is weighted by size, so a 50 megapixel image counts as 50 images and drops your effective speed to 10 images per minute.
💡 Size weighting catches people out. Resize a 48 megapixel phone photo to the dimensions you actually publish before you send it to any API.
Photoroom's Remove Background API has a sandbox mode: free calls that return a watermarked result. It is the safest place to wire up error handling, retries and file formats without spending anything. When you want to see real output, new accounts get 10 production calls on the Remove Background API with no watermark. Photoroom's pricing page also mentions 1,000 sandbox calls a month on the Image Editing API.
After that you buy a fixed amount, such as 1,000 or 2,000 images, from the API dashboard at $0.02 per image on the Basic plan.
The watermark is the trap. If your test pipeline points at sandbox and nobody flips the switch, watermarked product photos end up on a live store.
Bria's pricing page says its Trial "provides you with 100 free API calls." After that, background removal costs $0.018 per image on pay-as-you-go. PicassoIA's own Remove Background model comes from Bria, so the web tool and the API share a lineage.
Hair, fur and fine edges are where cutouts usually fail, so that is the first thing to test on any trial. A hundred calls is plenty for a proper comparison if you spend them deliberately instead of on stock product shots.
Once the free allowance is gone, pricing splits into two models: a flat price per image, or a charge per second of compute time. Each rewards a different kind of workload.
Flat prices are easy to budget. This table applies each listed rate at three volumes. Photoroom and Bria come from their own pricing pages, while Ideogram and Pixelcut come from fal's roundup of hosted background remover APIs.
| Provider | Per image | 1,000 images | 10,000 images | 100,000 images |
|---|---|---|---|---|
| Ideogram Remove Background (on fal) | $0.01 | $10 | $100 | $1,000 |
| Pixelcut Background Removal (on fal) | $0.016 | $16 | $160 | $1,600 |
| Bria Background Removal | $0.018 | $18 | $180 | $1,800 |
| Photoroom Basic plan | $0.02 | $20 | $200 | $2,000 |
remove.bg's paid credit packs and subscriptions are missing from the table because its public pages did not show rates we could verify. Check its pricing page for the current numbers.
Volume plans usually exist at the top end, so treat the 100,000 column as a starting quote, not a final one. Ask for a custom rate once you pass 50,000 images a month.
Some hosts bill per second of processing instead. On fal, BiRefNet v2 is listed at $0.0008 per compute second. If one image takes two seconds on that hardware, a cutout costs $0.0016, roughly six times cheaper than the $0.01 flat rate in the table above.
Treat that as an example, not a promise. Run 50 of your own images, read the billed seconds, and multiply. Compute billing also carries a hidden question: how does the host count cold starts and failed calls? Read the billing page before you queue a large batch.
rembg is the standard open source answer. It is MIT licensed, runs from the command line, from Python, as a local HTTP server or in Docker, and supports CPU, NVIDIA CUDA and AMD ROCm backends. There is no per-image fee, which makes it the only truly unlimited option on this page.
Install the CPU build, or swap cpu for gpu on NVIDIA hardware, then start the server:
pip install "rembg[cpu,cli]"
rembg s --host 0.0.0.0 --port 7000
The service then answers at http://localhost:7000/api. From Python, one file takes four lines:
from rembg import remove
with open("shoe.jpg", "rb") as src, open("shoe.png", "wb") as dst:
dst.write(remove(src.read()))
Docker users can skip the install: docker run -v .:/data danielgatis/rembg i /data/input.png /data/output.png.
rembg ships many models, including u2net, isnet-general-use and several birefnet variants. Switching between them is the fastest way to compare edge quality on your own images.
Budget for the costs the license does not mention:
Here is the catch most tutorials skip. The rembg code is MIT licensed, but model weights carry their own licenses. rembg's default model is bria-rmbg, and its README notes it is released under a BRIA license that requires a paid agreement for commercial use. So pip install with default settings is free for a hobby project and not free for a store.
Before you deploy, read the license for the specific model you select. The same README warns that some model weights need commercial agreements, so swapping models does not settle the question by itself.
When you need cutouts without writing code, the Remove Background model on PicassoIA runs in the browser. Its model page describes it as free and online, with no software to install. It returns a transparent PNG with an alpha channel and handles people, products, hair and objects.
Open the model page, then drop in a photo or paste an image URL. A URL saves a download and upload cycle when the photo already lives on your store or CDN. Start with a photo that has a clear subject, then move on to the hard ones.
The model exposes three switches:
| Setting | Default | What it does |
|---|---|---|
preserve_alpha | On | When switched off, the output is fully opaque instead of transparent |
preserve_partial_alpha | On | Keeps semi-transparent pixels from inputs that already have an alpha channel, and has no effect on plain photos |
content_moderation | Off | Screens inputs, useful when you handle photos in shared or public settings |
The model page presents the defaults as the soft edge setting for hair and an opaque option for hard edged product shots. Flip one switch on a single image and compare before you process a batch.
Save the PNG and place it on any backdrop. Need a fresh product shot to cut out? Generate one with PicassoIA Image, then run it through Remove Background. If the cutout needs a new scene behind it, PicassoIA Image Editor Pro edits an existing image from a text instruction.
💡 A web tool, not an API: at the time of writing, PicassoIA's developer API lists four models spanning image generation, image editing and video, and background removal is not one of them. For an automated pipeline, use one of the APIs above and keep PicassoIA for manual cutouts and for generating the source photos.
| Your situation | Best fit | Why |
|---|---|---|
| Weekend prototype | Photoroom sandbox or remove.bg previews | Free, renewing, and safe for wiring up the integration |
| Under 10,000 images a month, no ops team | Pay-as-you-go API from Bria or Photoroom | Flat price and no servers to maintain |
| Over 10,000 images a month | Hosted model billed by compute, or self-hosted rembg | Per-image cost can fall below $0.01, as the BiRefNet example showed |
| Commercial store using rembg | A model whose license allows commercial use | The default bria-rmbg weights need a paid agreement |
| A few manual cutouts a month | Remove Background on PicassoIA | No code and no setup |
Two rules of thumb sit behind the table. Below roughly 1,000 images a month, the cheapest option is whichever one you can integrate fastest, because the invoice is smaller than an hour of developer time. Above 10,000 images a month, run the numbers on self-hosting, because a single well-sized server can start undercutting per-image rates.
Vendor demos use flattering photos. Build your own test set of 20 images, five from each group:
Run every candidate over the set and check the edges at 200% zoom. Record failures instead of averages: a tool that nails 18 of 20 is a different product from one that nails 14, and that gap is invisible in a demo. Note the response time and the output file size too, because a 12 MB PNG per image changes your storage bill.
While you test, log three numbers for every call: latency, billed cost and output size. A provider that is a fraction of a cent cheaper per image but takes six seconds longer per call can cost you more in queue time than it saves on the invoice, especially when a customer is waiting on the page.
Pick the photo you actually need cut out, ideally the awkward one with wispy hair or a glass bottle, and run it through Remove Background on Picasso IA. It takes one upload and a few seconds, and it tells you more about edge quality than any pricing table can.
Then go one step further: generate a fresh product scene with PicassoIA Image, cut it out, and drop it onto whatever backdrop your store needs. If a free tier or a self-hosted server fits your volume, you now know what to build next. If you only need a handful of clean cutouts a month, the browser tool may be all you ever need. Open Picasso IA, experiment with your own images, and see how far free can go.
