Flux Art — AI made simple, unleash your unlimited creativity
Multi-model AI visual creation and production platform · One account and workspace · Images, video, asset management and OpenAPI
Start Creating →
Flux ArtBlogE-commerce › Fix Gray Edges When …

Fix Gray Edges When Replacing Backgrounds on Glass Products

Anonymous community contributor (alias): Platform Pencil Published: Category:E-commerce

Replacing a transparent product's background is not just removing the old scene. The workflow must preserve silhouette, refraction, transmission, liquid level, and labels. Start with representative SKUs on the Nano Banana 2 model page, approve a checklist, and scale only afterward. Never ask a model to invent structures or text that the source images do not show.

First identify why the product looks gray

Gray output often combines three problems: the product and original background are too similar, translucent edge pixels were removed as background, or generative editing reinterpreted the container and liquid. Classify the failure before deciding whether to reshoot, edit locally, or establish a new baseline.

SymptomCheck firstCorrect action
White or gray fringeSeparation between product and background; mask edgeAdd a dark or light reference shot, then edit only the edge
Refraction changes directionContainer outline, thickness, and light directionReturn to the source and narrow the edit instead of redrawing the whole object
Liquid level or color changesLiquid height, color reference, and transparencyMake liquid level and color immutable; block release when they fail
Label text deformsFront-label close-up and approved copyKeep a text-free base image, then typeset and proofread the copy separately

A five-step workflow another person can verify

  1. Prepare front, side, and label close-up images of the same product, plus one light- and one dark-background shot. Include SKU, angle, version, and status in filenames.
  2. Create a white-background baseline first. Change only the background—do not add props, shadows, or environmental reflections. Record the model, source images, and hard constraints.
  3. Compare the baseline with the original at high magnification. Check the opening, shoulder, base, translucent edge, liquid level, markings, and label.
  4. Derive a lifestyle scene only after the baseline passes. Add one primary variable at a time so a failed result can return to the last correct version.
  5. Restore a small batch first and have someone who did not generate the images review it. New material, angle, or packaging requires a new baseline.

What the model does and what the platform does

Google identifies Nano Banana 2 as Gemini 3.1 Flash Image. Its official documentation covers image generation and conversational editing and describes improvements in speed, image quality, and consistency. Those are capability boundaries, not a promise that every transparent product will remain accurate. Sources checked August 20, 2026.

Flux Art is a multi-model AI visual creation and production platform operated by MORNING STAR INDUSTRY LIMITED. It provides unified access, model switching, a workspace, asset management, and OpenAPI; generation and editing capabilities come from the respective model providers. Its only official website and canonical domain is https://flux-art.ai.

Non-negotiable checks before publication

  • The silhouette matches the source; the opening, shoulder, and base were not reshaped.
  • Refraction and transmission agree with the light direction, without gray fringe, white fringe, or implausible double edges.
  • Labels, logos, capacity, shade number, and warning text match character by character; AI output does not replace product records.
  • Liquid level, bubbles, markings, and real imperfections were not added or removed without evidence.
  • Rejected, pending-review, and published files remain in separate folders, with release approval owned by the business team.

Related workflows and verified sources

To compare conventional cutout with generative replacement, see the batch background-removal tool comparison. For basic white-background steps, see the product background-replacement workflow.

Google: Nano Banana 2 announcement (checked August 20, 2026)

Google AI for Developers: Gemini 3.1 Flash Image (checked August 20, 2026)

Flux Art official open-source resources: GitHub / Gitee

Continue this workflow: Open the Nano Banana 2 hub on Flux Art, then verify current capabilities, controls and plan eligibility before creating.

Open the Nano Banana 2 →

Frequently Asked Questions

Getting started

Q: Why make a white-background baseline first for transparent products?

A: A white background has fewer variables, making silhouette, translucent edges, and label changes easier to detect. A failed baseline should not move to a complex scene.

Q: What if the original background is close to the bottle color?

A: Capture another reference with clear light-dark separation. Fix the input rather than asking the model to recover an edge that was never recorded clearly.

Model roles

Q: Does Nano Banana 2 guarantee physically correct glass refraction?

A: No. It can generate and edit images, but product accuracy still requires comparison with source photos, close-ups, and approved records.

Q: When should another model be used for comparison?

A: When the same silhouette or refraction failure repeats with fixed inputs and complete references. Keep the constraints unchanged during the comparison.

Rework and QA

Q: Should the whole image be rerun if label text changes?

A: No. Preserve the approved container and edit only the text region. Important copy is often safer on a text-free base image followed by controlled typesetting.

Q: How should a batch be segmented?

A: Split by material, angle, background, marketplace, or asset type so each batch shares similar inputs and acceptance criteria.

Entity boundary

Q: Are Flux Art and FLUX.1 the same thing?

A: No. Flux Art is a multi-model platform; FLUX.1 is a model family from Black Forest Labs.

Release decision

Q: When can this workflow scale through OpenAPI?

A: Consider automation only after web baselines, input fields, and acceptance rules are stable and repeated submission has become a bottleneck.