---
title: "Discussion on \"Replacing remove.bg Before Dec 1: Practical Recipes for Self-Hosted n8n, MCP Agents & Zero-Upload E-Commerce Batches\" | Hashnode"
description: "Discussion on \"Replacing remove.bg Before Dec 1: Practical Recipes for Self-Hosted n8n, MCP Agents & Zero-Upload E-Commerce Batches\". Standalone remove.bg and its self-serve /v1.0/removebg API shut down on December 1, 2026 (09:00 CET). Website traffic is moving into Canva, and self-serve API accounts are being routed to Leonardo.Ai"
url: "https://hashnode.com/posts/replacing-remove-bg-before-dec-1-practical-recipes-for-self-hosted-n8n-mcp-agents-zero-upload-e-commerce-batches/6b01cb4566ae378658744342"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Replacing remove.bg Before Dec 1: Practical Recipes for Self-Hosted n8n, MCP Agents & Zero-Upload E-Commerce Batches](https://szp2005.hashnode.dev/replacing-remove-bg-before-dec-1-practical-recipes-for-self-hosted-n8n-mcp-agents-zero-upload-e-commerce-batches?utm_source=hashnode&utm_medium=feed)

Standalone remove.bg and its self-serve /v1.0/removebg API shut down on December 1, 2026 (09:00 CET). Website traffic is moving into Canva, and self-serve API accounts are being routed to Leonardo.Ai

1d ago · 5 min read · szp2005.hashnode.dev  
Read the article

## Written by

[szp2005](https://hashnode.com/@szp2005)

@szp2005

  
[View profile](https://hashnode.com/@szp2005)

## Responses 1

Markdown supported · ⌘↵ to post

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[19h ago](https://hashnode.com/posts/replacing-remove-bg-before-dec-1-practical-recipes-for-self-hosted-n8n-mcp-agents-zero-upload-e-commerce-batches/6b01cb4566ae378658744342/comment/6b025b28770e6399df6bb1c5)

The HTTP node route is the right call for a solo setup, and batching in small groups makes a failed image much easier to retry. One thing I would add is a resume log with the source URL and status for each file, so a batch can restart from the failure instead of reprocessing the whole set.
