If you’re using the remove.bg API, there’s something you need to take care of before December 1, 2026.<\/p>\n\n\n\n
That’s when remove.bg will shut down its self-service API, along with the website and other integrations. The cutoff is scheduled for 9:00 a.m. CET.<\/p>\n\n\n\n
For developers and businesses relying on remove.bg, this means finding another way to remove image backgrounds automatically. Whether it’s a product catalog, an upload form, or a script running in the background, those requests will need somewhere else to go.<\/p>\n\n\n\n
The good news is that you don’t necessarily need to rebuild your integration<\/strong>.<\/p>\n\n\n\n ShortPixel offers a remove.bg-compatible background removal API. If you’re using the supported request parameters, switching can be as simple as changing the API URL and your API key.<\/p>\n\n\n\n Here’s the difference:<\/p>\n\n\n\n – POST https:\/\/api.remove.bg\/v1.0\/removebg<\/p>\n\n\n\n + POST https:\/\/remove-bg-di.shortpixel.com\/v1.0\/removebg<\/p>\n\n\n\n – X-Api-Key: <your remove.bg key><\/p>\n\n\n\n + X-Api-Key: <your ShortPixel API key><\/p>\n\n\n\n That’s it for a standard request. The image upload, parameters, and response handling can remain the same.<\/p>\n\n\n\n Below, we’ll cover the migration process, the supported API options, and what it costs to use ShortPixel instead.<\/p>\n\n\n\n remove.bg became part of Canva in 2021. Canva is now moving the service’s background removal functionality into its own platform, which means remove.bg will no longer operate as a standalone product.<\/p>\n\n\n\n According to the official remove.bg FAQ<\/a>, several changes take effect on December 1:<\/p>\n\n\n\n There’s one more thing worth doing before the deadline: download any invoices or credit usage reports you might need. Once the account portal closes, you won’t be able to retrieve them.<\/p>\n\n\n\n Moving from one online background remover to another is usually easy. You upload a photo, remove the background, and download the image.<\/p>\n\n\n\n An API integration isn’t quite the same.<\/p>\n\n\n\n You might have a WooCommerce store that prepares supplier photos automatically. Or a website where customers upload images that need transparent backgrounds. In either case, remove.bg may be just one step in a process that already works well.<\/p>\n\n\n\n Changing that process to accommodate an entirely different API takes time.<\/p>\n\n\n\n ShortPixel’s compatible endpoint is intended to avoid most of that work. It uses the remove.bg request format, so you can keep your existing image handling and point the requests to ShortPixel instead.<\/p>\n\n\n\n This is particularly useful when the API is already integrated into your application and you simply need background removal to continue working after December 1.<\/p>\n\n\n\n First, you’ll need a ShortPixel account and API key.<\/p>\n\n\n\n You can create a free account here<\/a>. Once you’re signed in, find your API key in the account dashboard.<\/p>\n\n\n\n The next step is to replace the remove.bg endpoint with the ShortPixel-compatible one:<\/p>\n\n\n\n Your ShortPixel API key goes in the same X-Api-Key header you’re already using.<\/p>\n\n\n\n Here’s a basic request that uploads a JPEG and saves the background-free result as a PNG:<\/p>\n\n\n\n The structure is the same as a standard remove.bg request. You’re still sending an image file and choosing the output size.<\/p>\n\n\n\n We’ve specified size=auto to avoid relying on the default preview resolution, which may be too small for some uses.<\/p>\n\n\n\n If you’re using Python, here’s what the request looks like with the requests library:<\/p>\n\n\n\n Already have a Python integration? Compare the endpoint and authentication header with your existing code. For supported requests, those are the main changes.<\/p>\n\n\n\n For PHP and JavaScript, we’ve also prepared migration examples<\/a>.<\/p>\n\n\n\n You can find additional examples in our guide on removing image backgrounds with the ShortPixel API<\/a>.<\/p>\n\n\n\n If your automation uses a configurable HTTP request to call remove.bg, you can update that request without rebuilding the whole workflow.<\/p>\n\n\n\n Open the HTTP step, replace api.remove.bg with remove-bg-di.shortpixel.com, and use your ShortPixel key in the X-Api-Key header.<\/p>\n\n\n\n Some tools ask for a base API URL rather than the complete endpoint. In that case, use:<\/p>\n\n\n\n For WordPress plugins and third-party SDKs, check whether the API URL can be changed. If the remove.bg address is hardcoded, you may need to adjust the integration itself.<\/p>\n\n\n\n Either way, run a few images through the updated workflow before switching everything over.<\/p>\n\n\n\n ShortPixel’s remove.bg-compatible endpoint supports the common request options used for background removal.<\/p>\n\n\n\n Other supported parameters include format, type, type_level, and channels.<\/p>\n\n\n\n For example, if your current request sends an image using image_file and specifies size=auto, you can keep those options when moving to ShortPixel.<\/p>\n\n\n\n The API also follows remove.bg-style responses and error handling for supported operations. This helps existing code continue working without extensive changes.<\/p>\n\n\n\n Even when the code changes are small, it’s worth checking a few things before directing all your requests to the new endpoint.<\/p>\n\n\n\n Find every remove.bg request.<\/strong> Search your codebase for api.remove.bg. Check configuration files, scheduled scripts, plugins, and automation tools as well. You don’t want to discover an old integration after the API has already closed.<\/p>\n\n\n\n Update your credentials.<\/strong> Create your ShortPixel API key and store it securely, preferably in an environment variable or server-side configuration.<\/p>\n\n\n\n Check the output.<\/strong> Try representative images from your usual workflow. Look at the transparency, resolution, output format, and how your application handles the returned file.<\/p>\n\n\n\n Review error handling.<\/strong> Make sure failed requests are logged properly and that your application can handle unexpected API responses.<\/p>\n\n\n\nWhat’s happening to remove.bg?<\/strong><\/h2>\n\n\n\n
\n
Looking for a remove.bg API alternative?<\/strong><\/h2>\n\n\n\n
How to migrate to the ShortPixel API<\/strong><\/h2>\n\n\n\n
https:\/\/remove-bg-di.shortpixel.com\/v1.0\/removebg<\/a><\/code><\/pre>\n\n\n\nUsing cURL<\/strong><\/h3>\n\n\n\n
curl -f \\\n -H \"X-Api-Key: $SHORTPIXEL_API_KEY\" \\\n -F \"image_file=@photo.jpg\" \\\n -F \"size=auto\" \\\n -o no-bg.png \\\n https://remove-bg-di.shortpixel.com\/v1.0\/removebg<\/code><\/pre>\n\n\n\nUsing Python<\/strong><\/h3>\n\n\n\n
import os\nimport requests\n\nurl = \"https:\/\/remove-bg-di.shortpixel.com\/v1.0\/removebg\"\n\nwith open(\"photo.jpg\", \"rb\") as image:\n response = requests.post(\n url,\n files={\"image_file\": image},\n data={\"size\": \"auto\"},\n headers={\n \"X-Api-Key\": os.environ[\"SHORTPIXEL_API_KEY\"]\n },\n timeout=120,\n )\n\nif not response.ok:\n raise RuntimeError(\n f\"Background removal failed ({response.status_code}): \"\n f\"{response.text[:500]}\"\n )\n\nwith open(\"no-bg.png\", \"wb\") as output:\n output.write(response.content)<\/code><\/pre>\n\n\n\nUsing Zapier, Make, or another automation tool<\/strong><\/h3>\n\n\n\n
https://remove-bg-di.shortpixel.com\/v1.0<\/code><\/pre>\n\n\n\nWhat about the API parameters?<\/strong><\/h2>\n\n\n\n
Feature<\/strong><\/td> Supported options<\/strong><\/td><\/tr> Background removal<\/td> POST \/v1.0\/removebg<\/td><\/tr> Account information<\/td> GET \/v1.0\/account<\/td><\/tr> Image input<\/td> image_file, image_file_b64, image_url<\/td><\/tr> Input formats<\/td> JPG, PNG, WebP<\/td><\/tr> Input limits<\/td> Up to 22 MB and 50 MP<\/td><\/tr> Output sizing<\/td> preview, full, 50MP, auto<\/td><\/tr> Background settings<\/td> bg_color, bg_image_url, bg_image_file<\/td><\/tr> Response information<\/td> Image metadata and credit usage headers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Before you switch: a quick checklist<\/strong><\/h2>\n\n\n\n