Taskbar icon for Claude desktop app is heavily pixelated on Windows (MSIX missing targetsize assets)
<img width="1578" height="91" alt="Image" src="https://github.com/user-attachments/assets/cf280781-90f4-4ac0-b1ad-8caaf2b1e313" />
Taskbar icon for Claude desktop app is heavily pixelated on Windows
Environment
- App: Claude desktop (Windows, MSIX install from Microsoft Store)
- Version: 1.7196.0.0
- Install path:
C:\Program Files\WindowsApps\Claude_1.7196.0.0_x64__pzs8sxrjxfjjc\app\Claude.exe - OS: Windows 11 Pro 10.0.26200
- Status: Persistent across multiple app versions — has not been fixed despite passage of time.
Symptom
The Claude icon pinned to the Windows taskbar (and shown in the taskbar while the app is running) is visibly low-resolution and pixelated, in contrast to neighboring icons (Edge, File Explorer, Outlook, etc.) which render crisply at the same taskbar size and display scale.
Root cause — concrete evidence from the shipped MSIX package
The package declares Square44x44Logo.png as the taskbar icon source in AppxManifest.xml:
<uap:VisualElements
Square44x44Logo="Assets\Square44x44Logo.png"
Square150x150Logo="Assets\Square150x150Logo.png"
DisplayName="Claude" />
Inventory of the assets\ folder reveals two problems:
1. The two scale variants are byte-identical:
assets\Square44x44Logo.png 8222 bytes
assets\Square44x44Logo.scale-200.png 8222 bytes ← same byte count, almost certainly the same image
That means at 200% DPI scaling, Windows is being handed a 44×44 bitmap labeled as if it were 88×88. Result: upscale blur.
2. The targetsize-NN variant set required for crisp taskbar rendering across DPI is almost entirely missing.
Windows uses Square44x44Logo.targetsize-NN.png files to pick the right pre-rendered bitmap for the actual pixel size the taskbar needs (which varies by display scale and Windows version). The full recommended set is:
targetsize-16, -20, -24, -30, -32, -36, -40, -48, -60, -64, -72, -80, -96, -256
The package ships exactly one targetsize variant:
assets\Square44x44Logo.targetsize-24_altform-unplated.png 866 bytes
Every other size — including the larger sizes Windows 11's taskbar reaches for on high-DPI displays — is absent. So Windows falls back to upscaling the small Square44x44Logo.png, which produces the pixelation the user sees.
Compare to a well-packaged MSIX app such as the Windows Terminal or VS Code MSIX, which ship the full targetsize-NN and targetsize-NN_altform-* families.
Suggested fix
Regenerate the MSIX assets through the standard pipeline (Visual Studio's image-asset tool, MakeAppx, or Microsoft's UWP Tile Generator) starting from a high-resolution source SVG/PNG (≥256×256). Ensure the output includes the full set of Square44x44Logo.targetsize-*.png variants at minimum, plus matching scale-100/125/150/200/400 variants of each declared logo.
Impact
Cosmetic but persistent — the pinned Claude icon stands out (in a bad way) among other apps on the taskbar. For a polished Anthropic product this is more visible than most bugs, because users see it every single day.
Attachment
A screenshot showing the Claude icon next to other crisply-rendered taskbar icons can be attached at submission for direct visual comparison.
6 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is a deliberate re-file, not a duplicate.
The "possible duplicate" flagged by github-actions, #43211, is my own previous report from April 2026. It was closed as
invalid("Issue doesn't seem to be related to Claude Code") with no human comment, no fix, and no pointer to the correct tracker. The bug is still present in the current shipping version, 1.7196.0.0 (verified today against the live MSIX install atC:\Program Files\WindowsApps\Claude_1.7196.0.0_x64__pzs8sxrjxfjjc).There are two ways this report can move forward, and either is welcome:
If
anthropics/claude-codeis the wrong tracker for Claude Desktop bugsPlease:
CONTRIBUTING.md, in the issue templates, and ideally in the desktop app's own "Send feedback" / "Help" menu — so users don't repeat the same wasted cycle. Closing asinvalidwithout redirection trains users to either stop reporting or to keep refiling here.If
anthropics/claude-codeis the right tracker(The Claude Code product family is documented as including a Windows/Mac desktop app, and this MSIX package is how the CLI is distributed on Windows — so this reading is at least plausible.)
Then the original
invalidclose was a triage misfire. This new report contains stronger, falsifiable evidence than the original — verifiable in under a minute by anyone with the package installed:Square44x44Logo.pngandSquare44x44Logo.scale-200.pngare byte-identical (8,222 bytes each) in the shipping 1.7196.0.0 package. That means the scale-200 variant is not actually a 2× resolution asset — it's the 1× asset under a different filename. At 200% display scale, Windows hands the app a label saying "give me your 88×88 icon" and gets a 44×44 bitmap back, which it then upscales.Square44x44Logo.targetsize-NN.pngfamily that Windows uses for crisp taskbar rendering across DPI scales is almost entirely missing. The shipping package contains exactly one variant:Square44x44Logo.targetsize-24_altform-unplated.png(866 bytes). The full set Windows expects —targetsize-16, -20, -24, -30, -32, -36, -40, -48, -60, -64, -72, -80, -96, -256, plus matchingaltform-unplatedvariants — is absent.Compare to a well-packaged MSIX such as Windows Terminal or VS Code, which ship the complete
targetsize-NNfamily.The fix is a single asset-pipeline run from a high-resolution source PNG/SVG (≥256×256) through any standard UWP tile generator. The bug is not "the icon source art is low quality" — it is "the MSIX packaging step is skipping the assets Windows actually pulls from."
What I'm asking for
Either a reopen with a fix path, or a redirect to the correct tracker. Silent re-close is the only outcome that doesn't move things forward, and it's the outcome I'm trying to head off by writing this comment.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
I also have this issue. Why was this closed?
Exactly. This is a BUG. Please fix it.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.