remove.bg Is Shutting Down. I Built My Own Background Remover, and Here's Why
If you've ever worked with product photography, profile pictures, marketing graphics or image editing, there's a good chance you've used remove.bg. I personnally love the tool. It's one of those tools that makes a seemi
If you've ever worked with product photography, profile pictures, marketing graphics or image editing, there's a good chance you've used remove.bg. I personnally love the tool.
It's one of those tools that makes a seemingly complicated task incredibly simple: upload an image, remove the background and download the result.
However, remove.bg has announced that its standalone website and self-service API will be discontinued on December 1, 2026, with its background removal functionality moving into Canva.
That announcement got me thinking.
What happens to developers, designers, small business owners and everyday users who simply want a quick, straightforward way to remove an image background?
Interestingly, this is a problem I've already spent some time solving for myself.
How It Started
I originally built a background removal tool for my own use.
I needed something straightforward that would allow me to remove image backgrounds without going through an unnecessarily complicated workflow.
Rather than constantly switching between different applications and websites, I wanted something accessible, simple and convenient.
So I built one.
Initially, it was just a personal utility. Something I could use whenever I needed to process an image.
But as I continued building and experimenting with browser-based image tools, I realised there was an opportunity to turn these little utilities into something more useful.
I eventually rebuilt the experience with a better interface, a more polished workflow and a place within a larger collection of image and file utilities.
That's how this version came about.
Introducing the Vexelloom Background Remover
I've made the tool publicly accessible here:
Remove Image Background with Vexelloom
The goal is simple: make background removal accessible without making users navigate an unnecessarily complicated interface.
You can use it to remove backgrounds from images for things like:
- Product photography and e-commerce listings.
- Profile pictures and professional headshots.
- Marketing and promotional graphics.
- Presentations and creative projects.
- Social media content.
- General image editing.
I wanted the experience to feel straightforward. Upload an image, process it and get your result.
Why I Decided to Make It Public
I think there's something interesting about building tools to solve your own problems.
You understand the frustration because you've experienced it yourself. You know which steps are unnecessary, what makes a workflow inconvenient and what you would like to improve.
Sometimes, the best product ideas start with a simple question:
Why isn't there a simpler way to do this?
I also realised that a tool useful to me could be useful to thousands of other people facing the same problem.
Rather than keeping it as a personal utility, I decided to make it part of Vexelloom.
It's More Than Just a Background Remover
The background remover is only one part of what I'm building.
Vexelloom is a growing collection of browser-based tools for working with images, videos and documents.
The idea is to make everyday file-related tasks easier without requiring users to install multiple desktop applications for simple operations.
There are several other tools and utilities available, and I'm continuously working on improving the experience and expanding the collection.
You can explore everything here:
A Question for Other Developers
I'm curious about something.
Have you ever built a tool purely to solve a problem you personally experienced, only to realise that other people might find it useful too?
I'd also love to hear what you think about the move from standalone tools like remove.bg into larger platforms such as Canva.
Do you prefer having specialised, lightweight tools that do one thing well, or would you rather have everything integrated into one platform?
I'm looking forward to hearing your thoughts.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.