Most remove.bg failures in September-October 2026 are shutdown symptoms, not problems with your account or browser — the service is winding down ahead of its December 1, 2026 closure, producing intermittent 403s and broken uploads. This guide decodes each error message you may still see and lists working alternatives, including free local tools that need no credits. If your workflow depends on remove.bg, migrate now rather than waiting for the full shutdown.
Every "remove.bg not working" report we're seeing in September and October 2026 traces back to the same root cause: remove.bg is winding down its service ahead of the official shutdown date. Intermittent errors, 403 responses, and broken uploads are not bugs on your end — they're expected behavior during the transition to Canva and Leonardo.Ai.
When remove.bg fails, it usually shows a cryptic message. Here's what each one actually means during the shutdown period:
| Error | What It Means | Fix Available? |
|---|---|---|
| 403 Forbidden | Your account has been flagged, credits expired, or API key revoked during the Canva migration. | No fix |
| 401 Unauthorized | Session expired or API key invalid. Common when remove.bg rotates auth tokens during migration. | Workaround: relogin |
| 429 Too Many Requests | Rate limit hit. remove.bg has silently lowered free-tier limits ahead of shutdown. | Wait or switch |
| 503 Service Unavailable | Server is down for maintenance or being decommissioned. No ETA for recovery. | No fix |
| Upload stuck / timeout | Your image reaches the server but processing never completes. Backend AI pipeline is being throttled. | Retry smaller image |
| "Login failed" with correct password | Account already migrated to Canva. Your old remove.bg credentials no longer work. | Use Canva directly |
| Watermark appears on download | Free-tier quality has been degraded. HD output now requires credits you may not have. | No free fix |
Every retry consumes bandwidth and may flag your IP. If you've hit two errors in a row, accept that the service is degraded and move on. Don't waste an afternoon troubleshooting a tool that's being switched off.
Log in one last time and batch-process any images you have queued. Credits expire on December 1 with no refund and no transfer. Download everything you need today — don't wait for "next time."
Open a browser-based alternative like SmartImgKit Background Remover. It runs AI locally in your browser — no account, no server, no API key. If remove.bg's servers go dark, this tool keeps working because nothing depends on them.
If you had remove.bg bookmarked, integrated into a Zapier workflow, or used via Chrome extension, update those links now. Workflows pointing to remove.bg will start failing unpredictably before December 1.
If you're a developer who integrated the remove.bg API, the official migration path is Leonardo.Ai. Expect new pricing and a different API shape. Test the migration in staging before touching production.
remove.bg was acquired by Canva in 2021. For five years it operated as a semi-independent brand. In mid-2026, Canva announced it would fold remove.bg into its own design ecosystem, while the API business was sold separately to Leonardo.Ai. The standalone remove.bg website — the one most consumers know — closes permanently on December 1, 2026.
What you're experiencing now is the wind-down. Server capacity is being reallocated, free-tier limits are being tightened, and edge cases that used to work (like certain file formats or large image sizes) are silently breaking. This pattern will only accelerate as December 1 approaches.
| Period | Symptom | Root Cause |
|---|---|---|
| Sept – Oct 2026 | Intermittent errors, slower processing | Server reallocation to Canva |
| Nov 2026 | More frequent 403s, broken extension | API rate limits tightened |
| Dec 1, 2026 | Website completely offline | Service shutdown |
| Post-Dec 2026 | DNS may still resolve but no content | Domain redirects to Canva |
If you integrated remove.bg into your own application, the error patterns are different from consumer-side issues. Here's what developers are reporting:
Your API key is being rotated as part of the Leonardo.Ai migration. Check your email for a migration notice. If you don't receive one within a week, assume the key is permanently revoked and plan the Leonardo.Ai integration immediately.
The remove.bg API timeout was always 60 seconds for free tiers. Now it's hitting that limit consistently because the backend is overloaded with migration traffic. Retry logic with exponential backoff helps, but you should treat this as a signal to migrate rather than a transient issue.
A known issue during the wind-down: the API acknowledges the request but never processes the image. The response looks successful but contains no image data. Add a check for empty response bodies and treat them as failures.
remove.bg disabled webhook delivery as part of the migration. If your workflow relied on webhooks to trigger downstream processing, you'll need to switch to polling or migrate to Leonardo.Ai's webhook system.
Based on Canva's migration timeline and similar product shutdowns, November will be worse than September. Expect:
If you're reading this in November and remove.bg is still "sort of working," that's luck, not stability. Use the remaining days to fully migrate your workflow rather than waiting for the official shutdown date. For e-commerce sellers and graphic designers who built their entire production pipeline around remove.bg over the past five years, this wind-down is a massive operational disruption: suddenly the tool you relied on for every product photo is throwing random 403 errors, your API credits are expiring with no refund, and you have to rebuild your entire workflow from scratch in a matter of weeks. The good news is that browser-based local background removers like SmartImgKit now match the quality of cloud tools, because the open-source AI models have improved dramatically over the last two years, and they run entirely on your own device with no server dependency at all. That means you never have to deal with another situation where your core production tool shuts down overnight, taking your whole workflow offline with it. It also means your unreleased product photos, client headshots, and private images never get uploaded to a third-party server again, eliminating the whole category of privacy and security risks that come with cloud processing. Over the next few months, expect dozens of other cloud-based image tools to follow remove.bg's lead and start charging, cutting free tiers, or shutting down entirely — local browser tools are the only future-proof option, because there's no server to pay for, no company to shut the service down, and no credit balance that disappears when the business changes hands.
SmartImgKit runs entirely in your browser. No server to crash, no shutdown date, no credit expiration.
Use the Free Alternative →The shutdown process is gradual. Canva is moving traffic and server capacity in batches. Some requests still hit old infrastructure that works; others hit decommissioned servers that don't. That's why a reload sometimes "fixes" it — you got lucky on the next request.
No. The problem is not regional blocking or IP bans. It's server-side decommissioning. A VPN routes your request to a different exit point, but it still lands on the same broken backend. Don't waste time on this.
No. remove.bg's terms of service explicitly state that purchased credits are non-refundable and expire on the shutdown date. They will not transfer to Canva or Leonardo.Ai. Use them or lose them.
Browser caches and Wayback Machine snapshots may show old pages, but they won't process images — the AI backend is required for that. Any "downloadable remove.bg" clone you find online is either a fake, a malware bundle, or another cloud tool with its own shutdown risk.
It will stop working when the API shuts down. See our Chrome extension alternatives guide for replacements. Uninstall it now to avoid broken right-click menu items.
Why is remove.bg not working right now? Most likely because remove.bg is preparing for its December 1, 2026 shutdown. API servers are being throttled, accounts are being migrated to Canva, and the website may become unreliable. If you get a 403, 401, or timeout error, the service itself is the problem — not your computer.
What does remove.bg error 403 mean? A 403 Forbidden error means remove.bg's server rejected your request. During the pre-shutdown period this usually means your account has been flagged, your credits are expired, or the API key is being migrated to Leonardo.Ai. There is no fix on your end.
Why can't I log into remove.bg anymore? Account login issues are expected as remove.bg migrates users to Canva. If you signed up with Google or email, your account may already be queued for migration. Try logging in via Canva directly, or switch to a free alternative that doesn't require an account.
Is remove.bg permanently down? The standalone remove.bg website will be permanently shut down on December 1, 2026. After that date, the site will not be accessible at all. Any intermittent errors before then are part of the wind-down process.
What should I use instead of remove.bg right now? Switch to a browser-based tool like SmartImgKit. It runs AI locally in your browser, requires no account, and has no shutdown date. Your images are processed on your own computer and never uploaded anywhere.