Recent chats
ASKGEEZ Q&A GUIDETechnology & devices

Why do gradients show visible bands after I save an image?

Quick answer

Visible stripes in a smooth gradient can come from limited color information or heavy compression. [S1] Compare the saved file with your working image, then test an export with less compression if your app offers that control. If your editor has a debanding tool, try it on a copy. For Pixelmator Pro on Mac, the guide recommends changing the image to 16 bits per channel before using Deband. [S1]

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

Why do smooth gradients turn into stripes after I save the image? How can I tell whether the export is the cause?

Geez

The visible stripes are commonly called banding: a gradual color change appears as separate steps. Limited color information and heavy compression can contribute to it. [S1] Saving can expose or worsen the problem, but first check whether the bands are actually in the saved file rather than relying only on the editor’s preview.

Try this comparison:

  1. Reopen the exported file in your editor or view it in another image viewer.
  2. Compare it with the working image at the same approximate size and zoom.
  3. Export a second test copy with less compression, if the app provides that control.

If the saved copy shows stronger bands than the working image, export settings may be one contributor. If both show them, the gradient may already have limited color information. This comparison is a troubleshooting method, not proof of one specific cause.

Follow-up question

What should I change in the export settings first? I don't want to alter the original.

Geez

Keep the source project untouched and make a duplicate or a new export for each test. Change one thing at a time so you can tell which version looks better. If the export dialog offers a compression-quality control, test a less-compressed version and compare it with your current file. Heavy compression is a documented possible contributor, but the available guidance does not specify the right format, quality value, or settings for every app. [S1]

If your editor lets you choose color depth, check whether a higher-bit-depth working image is available before applying a banding fix. In Pixelmator Pro on Mac, the guide recommends changing the image to 16 bits per channel before using its Deband feature for best results. [S1] That instruction is specific to that application; it does not establish that other editors have the same command or behave identically.

Follow-up question

I use Pixelmator Pro on Mac. How do I try its debanding tool safely?

Geez

Work on a duplicate layer or project copy so you can compare the result and keep the unedited version. The Pixelmator Pro for Mac guide says to select a layer and choose Format > Deband; it also provides a before-and-after comparison. It recommends changing the image to 16 bits per channel before Deband for best results. [S1]

A simple test sequence is:

  1. Duplicate the project or layer.
  2. If appropriate for your workflow, change the image to 16 bits per channel.
  3. Select the target layer and choose Format > Deband.
  4. Inspect the before-and-after comparison, especially where the gradient is smoothest.
  5. Export a test and reopen it to check the saved result.

These steps are for Pixelmator Pro on Mac. The guide does not establish that debanding restores all lost detail or removes every visible band.

Follow-up question

Can you give me a short repeatable checklist for deciding whether the result is better?

Geez

Use the same gradient area and viewing conditions for each comparison. For example, if the working image looks smooth but the first export has visible steps, save a second test with less compression while leaving other settings unchanged. Compare the reopened file with the first export. If it looks better, you can use those settings for another test; if not, return to the project copy and change one other setting. This is a comparison method, not a promised result.

Record the app, chosen export settings, and which copy you inspected. Judge the reopened file, not just the export dialog’s preview. If banding remains, consider whether it was present in the working image and whether your editor provides a suitable debanding option. Avoid overwriting the original until you have checked the final saved file.

A practical checklist

  • Keep the source image or project unchanged; make a copy for experiments.

  • Reopen the exported file and compare it with the working image at a similar size.

  • If available, test less compression while keeping other export settings the same.

  • Change one setting at a time and note which copy you are comparing.

  • For Pixelmator Pro on Mac, consider the documented 16-bits-per-channel and Deband workflow, then inspect its comparison.

  • Check the final saved file before replacing or discarding the original.

A few more useful answers

Does saving as a different file format always remove banding?

No. The available guidance identifies limited color information and heavy compression as possible causes, but does not establish which format or settings will fix a particular image. [S1]

Will Pixelmator Pro’s Deband command work in other apps?

The cited instructions apply to Pixelmator Pro on Mac only. Other apps may use different tools or have no equivalent; the guidance does not establish their behavior. [S1]

Should I overwrite my working image after debanding?

Keep an unedited copy until you have compared the debanded version and reopened its export. That preserves a comparison point while you decide whether the result looks better.

Sources

References used for this guide.

  1. [S1] Remove color banding in an image in Pixelmator Pro on Mac
    support.apple.com · Checked

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work