Skip to content
Boring Doc
BreakingHigh impactOfficial migration guidesince 1.22.0ios

Cupertino icons 1.0.0

Framework · Official source

The existing cupertino_icons, 0.1.3 icons, are based on iOS 11 aesthetics with sharp angles and thin lines.

Original behavior

Not stated in the source.

New behavior

The new `cupertino_icons 1.0.0` font is handcrafted to best preserve the intent and aesthetic of the symbology through the transition. All existing `CupertinoIcons`' static `IconData` fields (and thus all of the font `.ttf`'s codepoints) continue to work and point to a reasonable new icon.

Who is affected
affects the following icon groups:
Practical impact
Behaviour or API differences that can break builds or change runtime behaviour.
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:CupertinoIconsIconData
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)

After upgrading to 1.22, if you also upgrade the cupertino_icons pubspec dependency from 0.1.3 to 1.0.0, for example, by changing:

dependencies:
  ... // Other dependencies
  cupertino_icons: ^0.1.0

to:

dependencies:
  ... // Other dependencies
  cupertino_icons: ^1.0.0

All your CupertinoIcons should automatically update to the new aesthetic (except for the unchanged icons listed above).

At this point, you can also explore [CupertinoIcons][] for new icons to use in your application.

You're encouraged to verify your application after migrating to ensure that the automatically mapped new icons are suitable for your desired aesthetics.

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 (95%)

Listed in the official breaking-changes index (docs.flutter.dev/release/breaking-changes).

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?