The BackgroundErase Zapier integration lets you remove image backgrounds as part of an automated Zap. You can process a file from a previous step, process an image URL already present in your workflow, or use the universal API action for advanced BackgroundErase requests.
Best fit: Use this integration for catalog cleanup, ecommerce image workflows, Airtable attachment processing, Shopify product image updates, CMS asset cleanup, folder watches, Google Drive or Dropbox automations, form uploads, and internal operations flows where Zapier already moves the image.
Install the Zapier integration
Start by opening the BackgroundErase Zapier integration. If your team is using a private invite link, open that invite while signed in to Zapier.
Create and connect an API key
BackgroundErase uses API key authentication. Zapier stores the key in your BackgroundErase connection and sends it automatically as x-api-key.
- Create a Business account BackgroundErase API access is available on Business and Enterprise plans.
- Generate an API key Open your BackgroundErase account page, create an API key, and keep it private while you connect Zapier.
- Connect BackgroundErase in Zapier When Zapier asks for a BackgroundErase connection, paste the API key. Zapier stores it in the connection and sends it automatically.
Keep the key inside the Zapier connection. Do not expose it in public forms, spreadsheet columns, browser code, or Zap outputs.
- API base: https://api.backgrounderase.com
- Authentication test: GET /v2/account
- Main processing endpoint: POST /v2
- Dedicated image actions use multipart/form-data.
How billing works
BackgroundErase uses metered monthly billing for Zapier automations. Each successfully processed image counts as one billable image for the billing period.
The Zapier actions return billing fields such as billing_model, usage_unit, and billable_units so your team can understand how Zap runs map to BackgroundErase usage.
Choose the right action
Most workflows should use one of the two dedicated background removal actions. The universal API action is for advanced requests and account checks.
Remove Background From File
Use this when an earlier Zap step gives you a file object or downloadable file from Google Drive, Dropbox, OneDrive, Box, an email attachment, form upload, or HTTP file download.
Remove Background From Image URL
Use this when your Zap already has a public or signed image URL from Airtable, Shopify, Webflow, Google Sheets, a webhook, or an external CMS.
Make an API Call
Use this for advanced API requests, account checks, future endpoints, custom workflows, or debugging authenticated calls.
Walkthrough: remove background from a file
Use Remove Background From File when an earlier Zap step provides a file object or downloadable file. The action sends the file to BackgroundErase as multipart/form-data using the image_file field and returns the processed image as a Zapier file output.
- Add a trigger or source step that finds or receives an image, such as Google Drive, Dropbox, Airtable, Typeform, Gmail, or a form upload.
- Add a download or get-file step if the trigger only provides metadata.
- Add BackgroundErase > Remove Background From File.
- Map File Name from the source filename.
- Map File Data from the file object or downloaded file.
- Choose output options: transparent PNG, WebP, JPG with background color, crop, despill, or alpha mask.
- Use Test step to confirm the action returns a file.
- Send the returned file output to another Zapier step, such as Google Drive Upload File, Airtable update record, Dropbox upload, Shopify product update, CMS upload, or cloud storage.
File Name
Required. Map the original filename of the image to process.
File Data
Required. Map the Zapier file input from a previous step.
Output Type
Required. Defaults to Transparent Image. Choose Transparent Image or Alpha Mask.
Output Format
Required. Defaults to PNG. Choose PNG, WebP, or JPG. PNG is recommended for transparency, and alpha mask output is always PNG.
Size
Required. Defaults to Full. Choose Preview, Medium, HD, Full, or Auto.
Optional cleanup
Use Crop to Subject, Remove Green Spill, or Background Color when the destination needs tighter framing, despill, or a flattened color such as #FFFFFF or white.
If you are unsure which action to use, start with the file action. It avoids many URL permission issues because Zapier passes the image file directly to BackgroundErase.
Walkthrough: remove background from an image URL
Use Remove Background From Image URL when the Zap already has a public or signed image URL. The action sends the URL to BackgroundErase as multipart/form-data using the image_url field. BackgroundErase fetches the image server-side and returns the processed file.
- Start with a trigger or step that provides an image URL, such as Airtable, Shopify, Webflow, Google Sheets, a webhook, or an external CMS.
- Add BackgroundErase > Remove Background From Image URL.
- Map the URL into Image URL.
- Optionally set Output Base Name.
- Choose output type, format, size, crop, despill, and background color.
- Use Test step to confirm the action returns a file.
- Save the returned file output to storage, attach it to a record, update a product image, or pass it into another Zapier app.
Image URL
Required. Map a publicly reachable URL or signed URL for the image to process.
Output Base Name
Optional. Controls the output filename base. If blank, the output defaults to backgrounderase-image_output.
Output Type
Required. Defaults to Transparent Image. Choose Transparent Image or Alpha Mask.
Output Format
Required. Defaults to PNG. Choose PNG, WebP, or JPG.
Size
Required. Defaults to Full. Choose Preview, Medium, HD, Full, or Auto.
Optional cleanup
Use Crop to Subject, Remove Green Spill, and Background Color as needed for your destination app.
The URL must be reachable by BackgroundErase's backend. Private Google Drive links, expired signed URLs, login-protected URLs, and internal network URLs may fail. If that happens, download the file in Zapier first and use Remove Background From File instead.
Universal API action for advanced calls
The Make an API Call action is for advanced BackgroundErase requests. Use it to call an endpoint directly, test a new API parameter, debug authentication, or check account status.
- URL: /v2/account
- Method: GET
- Headers: {}
- Query String: {}
- Body: empty
The response should show whether the API key is valid and what billing model the account uses. For normal image processing, use the dedicated file or URL actions instead. They provide a cleaner interface and return the processed image as a file output ready for downstream Zapier steps.
Output fields
The dedicated image actions return a processed file plus usage fields you can map into later Zap steps when needed.
Remove Background From File
File Name, File Data, MIME Type, Billing Model, Usage Unit, and Billable Units.
Remove Background From Image URL
File Name, File Data, MIME Type, Billing Model, Usage Unit, Billable Units, and Source URL.
Make an API Call
Body, Headers, and Status Code.
Supported options
The file and URL actions expose the same practical controls as the BackgroundErase API. Start simple, then add options as your destination app requires them.
Output Type
Choose Transparent Image for normal cutouts or Alpha Mask when the next step handles compositing.
Format
Choose PNG, WebP, or JPG. PNG is best for transparency. Alpha mask output is always returned as PNG.
Size
Choose preview, medium, HD, full, or auto depending on how much detail the downstream app needs.
Crop
Enable Crop to Subject when you want the output trimmed around the detected foreground.
Despill
Enable Remove Green Spill for green-screen style photos where color bleed appears around edges.
Background Color
Set Background Color to flatten the result onto a color such as #FFFFFF or white. Leave it empty for transparent output.
For the full API reference, see the request fields and flags docs.
Limits to know before you turn on a Zap
- Max file size: images can be up to 30 MB.
- Max pixels: source images can be up to 100,000,000 pixels.
- Private URLs: image URLs must be reachable by BackgroundErase.
- Login-protected URLs, expired signed URLs, private Drive links, and internal network URLs may fail.
- The dedicated file and URL actions use multipart/form-data automatically.
- Alpha mask output is always PNG.
- JPG output does not preserve transparency, so use a background color or expect a flattened image.
Troubleshooting common Zapier errors
Invalid API key
Reconnect the BackgroundErase app in Zapier and paste a fresh API key from your account. Zapier adds the x-api-key header through the connection, so you should not add it manually.
API key helpImage too large
BackgroundErase accepts images up to 30 MB and 100,000,000 pixels. Resize the source image or use a smaller export before sending it through the Zap.
Size helpPrivate image URL
The URL action can only process URLs that BackgroundErase can fetch from its backend. Private Drive links, expired signed URLs, login-protected URLs, and internal network URLs may fail.
URL helpBad background color
Use a valid hex color such as #FFFFFF or a supported named color such as white. If you do not need a flattened background, leave Background Color empty.
Color helpNo file data from previous step
Some Zapier triggers only provide file metadata or a web page link, not the actual file. Add a download or get-file step before Remove Background From File.
Output file will not upload to the next app
Map the BackgroundErase File Data output, not just the file name. If the next app also asks for a filename, map the BackgroundErase File Name output.
Support and API docs
If a Zap fails and troubleshooting does not resolve it, contact BackgroundErase support with the action name, the error message, whether the Zap used a file or image URL, and the destination app receiving the output file.