Images Agents Pricing Docs Blog View as Markdown (Agent) Get started
Human Agent
For e-commerce

One product photo.
Every variant your catalog needs.

Upload the master once. Get white-background marketplace images, responsive listing and product-page sizes, and watermarked copies straight from the URL, served from a global CDN with zero egress fees.

See the recipes
One product photo passing through a vault and fanning out into a white-background cut-out, a thumbnail, a social card and a watermarked copy

Recipes that work today

Replace the path with your own image. Each variant is generated on the first request, then cached at the edge for a year.

Marketplace main image

AI cut-out on pure white, centered on a 2000×2000 square. Marketplaces and shopping feeds typically ask for this; check each one's current rules.

Tan leather sneaker photographed on a wooden table
Original upload
The same sneaker cut out on a pure white square
Same params, shown smaller
.../proj_xyz789/img_abc123.jpg
  ?segment=foreground&background=white
  &w=2000&h=2000&fit=pad

Output is PNG. Add fmt=webp for a much smaller file.

Listing and product-page sizes

Square crops for category grids, a larger version for the product page. Modern browsers get AVIF or WebP; others get JPEG.

Square 640 pixel crop of the sneaker photo
640×640 · 25 KB as AVIF (the master is 483 KB)
.../img_abc123.jpg?w=640&h=640&fit=cover&fmt=auto
.../img_abc123.jpg?w=1200&fmt=auto

In our test, a 1200 px variant of a 700 KB master was 99 KB as AVIF versus 147 KB as JPEG.

Thumbnails

Cart, search and email thumbnails cropped around the subject.

200 pixel square thumbnail of the sneaker photo
200×200 · 8 KB
.../img_abc123.jpg?w=200&h=200&fit=cover&gravity=auto

Social and link-preview cards

A 1200×630 card for Open Graph and ads, from the same master.

1200 by 630 social card crop of the sneaker photo
1200×630 · 74 KB
.../img_abc123.jpg?size=social

Transparent cut-out

Drop the product onto your own backgrounds and banners.

Tan leather sneaker photographed on a wooden table
Original upload
The sneaker cut out with a transparent background
Transparent cut-out
.../img_abc123.jpg?segment=foreground

Delivered as a transparent PNG (or WebP/AVIF with fmt).

Watermarked copies

Upload your watermark once, with the opacity baked in, and tile it over any image in the same project.

Tan leather sneaker photographed on a wooden table
Original upload
The sneaker photo with a tiled SAMPLE SHOP watermark
Tiled with a 260×140 PNG, 45% opacity
.../img_abc123.jpg?w=1200&tile=img_wm123.png

tile takes the watermark's image id and extension. It tiles edge to edge; there is no corner-logo placement yet.

Automate it

Re-host supplier images

Import from a supplier URL with one call. dedupe skips identical files, so a nightly job doesn't store copies. Batch import takes up to 50 images per request, each with its own metadata.

curl https://api.pixelvault.dev/v1/images \
  -H "Authorization: Bearer $PIXELVAULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://supplier.example.com/img/1234.jpg","folder":"sku-1234","dedupe":true}'

No-code pipelines

New product row, import the image, write the variant URLs back to your sheet or store. Ready-made Shopify and WooCommerce workflows for n8n, plus Make and more.

Agent-run catalog cleanup

Point Claude, Cursor or any MCP-capable agent at a folder of product shots and let it upload, build the variant URLs and report back. See PixelVault for AI agents.

Use it with your agent

The pixelvault-ecommerce-catalog skill gives Claude Code, Codex, Cursor and other agents that read SKILL.md the whole flow: upload each photo once, build the variants above, check every result against what was asked for, and report a SKU-to-URL table. It knows the traps listed below, including that invalid parameters are ignored silently.

1. Install the skills, then run /pixelvault-setup to add your API key:

npx skills add pixelvault-dev/skill

2. Ask your agent:

Using PixelVault, make marketplace-ready white-background versions of the product photos in ./products, plus 640px listing and 1200px product-page sizes, and give me a table of SKU and URLs.

Prefer MCP? Point your agent at https://mcp.pixelvault.dev/mcp and use the recipes above. Read the skill.

Good to know

  • Cut-outs, effects and watermarks need a project with an API key. They don't apply to anonymous test uploads.
  • Sizes snap up to the nearest supported step (16, 32, 48, 64, 96, 128, 200, 256, 320, 400, 512, 640, 800, 1024, 1200, 1600, 2000, 2400, 3000, 4000), so a request for 1500 returns 1600. Variants never exceed the source size.
  • A cut-out can't be JPEG. It's PNG, WebP or AVIF. Requesting JPEG returns PNG.
  • Unsupported or invalid parameters are ignored and the original is served, never an error. Check a recipe once before running it over a whole catalog.
  • Importing from a URL needs a direct link. Redirects are refused, and some hosts block server-side fetchers; for those, download the file and upload it. Folder names take letters, numbers, hyphens and underscores only (sku-1234, not skus/1234).
  • The first request for a new cut-out takes a couple of seconds. Request your variants once after import to warm the cache.
  • Size your plan to the catalog. Storage is 5 GB on Starter and 25 GB on Pro; see pricing.

Coming, and we want your input

  • Shopify and WooCommerce connectors
  • Bulk import from a CSV or product feed
  • Look up images by SKU or metadata
  • Webhooks when an image is processed
  • Your own domain for images (cdn.yourstore.com)

Tell us about your catalog

What store platform, roughly how many products, and what you use for images today. We'll email you once, to talk. No newsletter, no spam.

Email us about early access

Want to try the recipes first? Start free with 200 MB and 500 uploads/month.