Skip to content
Boring Doc
DeprecatedMedium impactOfficial migration guidesince 3.16.0landed 3.14.0-0.1.pre

Deprecated Paint.enableDithering

Framework · Official source

`Paint.enableDithering` is now `true` by default (previously, `false`), and is _deprecated_ pending removal - Flutter no longer supports user-configurable dithering settings.

Who is affected
Code that still calls the deprecated API; it keeps working until removal but produces analyzer warnings. Code that uses Paint.enableDithering.
Practical impact
Warnings now; removal in a future release. Plan the migration but no immediate break.
What action should I take?
Follow the official migration guide below, update affected call sites, run `dart fix --apply` where a fix is available, then run your tests.
APIs mentioned:Paint.enableDithering
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)

Most users and libraries will not need to make any changes.

For users that maintain golden tests, you might need to update your golden images to reflect the new default. For example, if you use [matchesGoldenFile][] to test a widget that contains a gradient:

$ flutter test --update-goldens

While this is not expected to be a common case, you can disable dithering temporarily by setting the enableDithering property in your main() method (either in an app or test):

  void main() {
+   // TODO: Remove this after XYZ.
+   Paint.enableDithering = false;

    runApp(MyApp());
  }

As the plan is to permanently remove the enableDithering property, please provide feedback in [Issue 112498][] if you have a use case that requires disabling dithering (due to performance, crashes).

If you must draw gradients without dithering, you can write a custom fragment shader. Describing how to write shaders is outside the scope of this migration guide. For more information, refer to Writing and using fragment shaders.

NOTE: Flutter web does not support dithering: [Issue 134250][].

Migration assistantAI-generated · grounded in cited sources
AI explanations are not configured
Set AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.
Official migration guide·Verified classification (90%)

Listed in the official breaking-changes index; title states deprecation.

An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.

Source commit
b3045439b7c0
Source last updated
Oct 21, 2026
Last synchronized
Oct 21, 2026
Publication status
published
Publication history
  • Oct 21, 2026, 8:31 PM: new → published (ingestion) — Backed by an official breaking-change/migration guide.
AI explanationAI-generated · grounded in cited sources
AI explanations are not configured
Set AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.
Was this useful?