QuokkaPix
Home Google Merchant images

Resize image

Prepare product images for Google Merchant workflows

Google Merchant image preparation is about consistent product presentation, not just one pixel size. Start with a clean product image, keep the subject clear, and export files that your feed workflow can map back to the source.

Product feedsWhite backgroundManifest checks
Open live editor Resize image
The button below opens the QuokkaPix editor with this tool already selected.

Good fits

1
Prepare product photos before feed upload.
2
Create consistent square or catalog-ready exports.
3
Run agent recipes with source-to-output mapping.

Workflow

1
Upload a representative product image.
2
Choose a catalog size or product image recipe.
3
Check background, subject framing and output format.
4
Export and review sourceName to outputName mapping.

Limits to check

1
QuokkaPix does not submit the feed to Google.
2
Category-specific rules still need source-backed profile checks.
3
Visual content such as text overlays or watermarks must be reviewed before publishing.

FAQ

Is this a feed validator?

No. It prepares image assets and exposes manifests; feed validation is a separate step.

Can agents run this?

Yes. Agents can use official recipes and sourced rule profiles where available.

Practical QA notes

Merchant image QA

1
Keep the product clearly visible and not cropped.
2
Use consistent background and canvas decisions across a catalog batch.
3
Check file names and output counts before feed handoff.
4
Use sourced rule profiles instead of guessed requirements.

Merchant image resizing must stay tied to catalog QA

Google Merchant preparation is not only a size preset. The image has to remain a trustworthy product asset that can be mapped back to the source and checked against the destination rules. Resize the canvas, but also review background, product scale, edge clearance, file naming and whether the output belongs to the correct product group. QuokkaPix can prepare local image files and result manifests; feed validation, category policy and final merchant review remain separate checks.

1
Keep one product group per batch when QA needs to be meaningful.
2
Check sourceName and outputName before uploading to a feed workflow.
3
Use sourced rule profiles instead of guessed marketplace requirements.

Separate feed readiness from visual polish

For Google Merchant, a resized file is useful only when the feed can still explain the product clearly. Check the main product image separately from lifestyle or detail images: the main image needs a direct view, clean framing and enough product scale, while secondary images can show context. Keep the exported batch grouped by product or SKU so the manifest, filenames and catalog rows stay easy to reconcile.

1
Review the product scale in the smallest feed preview.
2
Keep one product group per batch when possible.
3
Treat platform approval as a catalog check, not just an image-size check.

Keep catalog evidence reusable

A Google Merchant export should be repeatable when a catalog row is edited later. Keep the selected preset, output size, source filename and exported filename together so another person can rebuild the same image set without guessing. This matters most when a product has variants: a white item, a dark item and a detail crop can all pass size checks while still creating inconsistent catalog presentation.

1
Keep source and output names aligned with SKU or product ID.
2
Save one reference export before running a large batch.
3
Review variant images together, not as isolated files.