arthur197Q: Has it been actively developed over the last couple of years? (It does not look like to me)
I remember looking at BackgroundCut a couple of years ago and, to be honest, it didn’t feel very active at the time. Some features, like the Chrome extension, seemed to be stuck in “coming soon” for a long while.
I’m checking it again now, but I’m not immediately seeing what has changed or improved since then. I’d like to understand whether the product is still being actively developed.
Could you share a clear update on what has changed in the last 12–24 months? Roadmap progress, or any public changelog/release notes.
Harsh_Ranjan
Jul 4, 2026A: Hey,
Thanks for using BackgroundCut, and that's a fair question, let me give you an honest and clear picture.
You're right that visible development felt slow for a while, and I won't pretend otherwise. The Chrome extension and plugins are a good example, I did release Figma and WooCommerce plugins, but they never gained real traction, so I stepped back from actively updating or releasing new ones rather than sinking time into something few people used.
That said, here's what's genuinely changed in the last 12-24 months:
1. A brand new photo editor, with object selection for accurate cutouts, and an image matting feature (great for fine detail like hair). Both run on backend GPU compute rather than lightweight browser models, which is what gives the accuracy.
2. Reworked upload flow, the separate bulk remover page has been removed and folded into the main upload page. You can now do multiple uploads, select/replace backgrounds, and use auto-crop all from one place.
3. A new API v3, alongside the existing versions.
4. A lot of backend work, architecture changes and stability improvements that aren't directly visible but matter for reliability.
So the honest summary is: the product is actively developed, but a lot of the work over this period went into architecture, stability, and the new editor rather than flashy front-end features, so it may not jump out immediately.
On the roadmap, I'm currently working on an image generation model. The architecture is set up, and I'm mainly evaluating viability right now, since GPU compute costs for generation are significant. I'm also considering a BYOK (bring your own key) option, where you could plug in your own API key for background image generation, which would help keep it affordable.
Happy to answer anything more specific about any of these!
Thanks,
Harsh Ranjan
Founder, BackgroundCut