4K image generation produces repeating tiled background artifacts after migration from Preview to Image

We are experiencing a reproducible image-generation issue using Google image-generation models.

The issue occurs not only through Replicate, but also through a Vertex AI API access path.

The issue started only after the transition from the previous Preview version to the current Image version.

It affects both:

  • Gemini 3 Pro Image
  • Gemini 3.1 Flash Image

The problem appears specifically when generating images at 4K resolution.

When one or more reference images have a bright, light, or white background, the generated result may contain large repeating square texture patches across the background. Instead of producing a uniform white background, the model creates tiled, fabric-like or paper-like patterns with visible repetition and soft boundaries between the patches.

The main product is often generated correctly, while the background around it is corrupted.

We did not observe this behavior with the previous Preview version. The issue began only after switching from Preview to Image.

This behavior appears regardless of whether the output format is set to PNG or JPG/JPEG.

Expected result

A product image with a clean, flat and uniform white background, without textures, panels, tiles, repeated patterns or additional background elements.

Actual result

At 4K resolution, the generated image contains large repeating background tiles. Similar texture patches are duplicated across the image, especially in areas that should be plain white.

Conditions under which the issue occurs

  • Access path / provider:
    • Replicate
    • Vertex AI API
  • Model family affected:
    • Gemini 3 Pro Image
    • Gemini 3.1 Flash Image
  • Input type: image-to-image generation using reference images
  • Reference-image background: usually bright, light grey, or white
  • Requested background: plain white
  • Output resolution: 4K
  • Output format: PNG and JPG/JPEG both affected
  • Aspect ratio: 1:1
  • Fallback model: disabled (where applicable)

Reproduction code

import Replicate from "replicate";
const replicate = new Replicate();

const output = await replicate.run(
  "google/nano-banana-pro",
  {
    input: {
      allow_fallback_model: false,
      aspect_ratio: "1:1",
      image_input: [
        "https://api.replicate.com/v1/files/MTFmYzdmYjEtMDI0NC00NmFmLWI4ZmEtYjA4M2JhMTQ3NDJl.jpg"
      ],
      output_format: "png",
      prompt: "create a new design of this shoe, plain white background",
      resolution: "4K",
      safety_filter_level: "block_only_high"
    }
  }
);

console.log(output);

Steps to reproduce

  1. Use a shoe or product reference image with a bright or white background.
  2. Run image-to-image generation through the Replicate API.
  3. Use the model endpoint google/nano-banana-pro.
  4. Set resolution to "4K".
  5. Request a plain white background.
  6. Inspect the generated background.

Additional observations

  • The issue is reproducible through Replicate and also through a Vertex AI API access path.
  • This suggests that the problem may not be limited to Replicate-side processing.
  • The artifact is strongly associated with 4K generation.
  • The same workflow did not produce these tiled background artifacts with the previous Preview version.
  • Bright or white areas in the reference image appear to increase the likelihood of the problem.
  • Prompting the model more explicitly for a uniform white background does not reliably prevent the artifact.
  • The issue occurs regardless of whether the output is requested as PNG or JPG/JPEG.
  • The repeated patches suggest a possible issue in the 4K upscaling, tiling, outpainting, or high-resolution decoding pipeline.

Regression information

This appears to be a regression introduced after the transition from the previous Preview model/API version to the current Image version.

Request

Please investigate whether the 4K generation pipeline is incorrectly applying tiled texture synthesis to bright or white background regions.

I see this issue too, it manifests a little differently and less obvious but feels connected.

The timing also feels similar… didn’t notice it until the last month.

Our workflows are similar:

  • Use product photography as input (apparel, footwear, accessories)
  • Place that product photography on a person in a studio that varies from pure white to simple flooring and backdrops

We are seeing artifacts such as:

  • subtle value “stripes” in skin that sometimes continue into the solid color backgrounds
  • a crunchy noisy square in the upper left corner of images

Our workflows constantly evolve, but I have only started noticing it in the last month or so… it feels like a change with the model.

I will try to put together some generic examples to share here.

This issue seems related and the timing also lines up: Edge case: intricate products + high resolution + plain white background → blurred / partially-rendered output (Nano Banana)

Hi @GW-Grafik @Conor_Fitzgerald
I am looking into this and will share an update

+1 here. We’ve been seeing this for the last month and has been a huge pain to deal with.

I will leave my other two issues here aswell that I have experienced since switching from the preview to the normal models. It always affects the 2k and 4k version and image to image generation, so my take is that its some kind of an upscaling problem.

Here’s an example that feels similar which we are seeing in our production workflows. In studio shots with simple backgrounds and floors, we often get a noisy square on in the top left.

Uploading here seems to reduce my images from 4k, I’d be happy to share the originals if it helps.

Original:

Then:
“change her apparel to a navy sweat suit”

Zooming in on the upper left, we see a noisy square. The rest of the background looks pretty good and smooth:

This artifact is most often present at 4k, when generating 16:9 images. This is an average example, it can be more or less severe but is reproducible. We began noticing this change around a month ago and have not found a solution aside from generating lower resolution or different aspect ratios.

These images also demonstrate the pink color shift mentioned above by @GW-Grafik

Hi @Mustan_lokhand just wanted to follow up; any luck finding the issue here? I tried getting in touch via DM but not sure if it went through. I’d be glad to reproduce this on a call.

Hey @Conor_Fitzgerald

I was able to reproduce this issue and have informed the team internally about it

Will keep this thread updates