Skip to content

fix: update Blender logo to upstream version#3285

Merged
PKief merged 5 commits intomaterial-extensions:mainfrom
mcgrathd:vscode-material-icon-fix-blender-logo
Jan 13, 2026
Merged

fix: update Blender logo to upstream version#3285
PKief merged 5 commits intomaterial-extensions:mainfrom
mcgrathd:vscode-material-icon-fix-blender-logo

Conversation

@mcgrathd
Copy link
Copy Markdown
Contributor

@mcgrathd mcgrathd commented Dec 5, 2025

It was noticed in the Blender community chat that the logo used in Gitea appeared to come from the material-extensions source, but was not using the correct logo.

The guidelines and design for the logo can be found at:

https://www.blender.org/about/logo/

This patch attempts to honor the spirit of the replaced logo, while following the "slanted" look of the upstream logo.

Description

Replace the current logo with the upstream logo.

Contribution Guidelines

It was noticed in the Blender community chat that the logo used in Gitea appeared to come from the material-extensions source, but was not using the correct logo.

The guidelines and design for the logo can be found at:

  https://www.blender.org/about/logo/

This patch attempts to honor the spirit of the replaced logo, while following the "slanted" look of the upstream logo.
@github-actions github-actions bot added the icons PR with new icons label Dec 5, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Dec 5, 2025

Preview

Thank you for creating a pull request. This preview shows you how your icons will look on the different themes:

Generated preview

Check how your icons fit in a 16x16 grid with our Pixel Perfect Checker by following this link.

You can find more information on how to contribute in the contribution guidelines.

@bartvdbraak
Copy link
Copy Markdown

Looks good!

@lucas-labs
Copy link
Copy Markdown
Member

Hi! Thanks for you PR!

The blender logo in our current icon is not exactly the same as the official blender logo, because ours was especially made to be pixel perfect at 16x16 px (which is the size vscode renders icons by default). Look here: #3046

image

IMHO, the current icon renders sharper at 16px and the difference between our icon and the upstream version is not big enough to be noticeable at such small size.

@bartvdbraak
Copy link
Copy Markdown

bartvdbraak commented Dec 9, 2025

Hi @lucas-labs, me and @mcgrathd are part of the Blender project and community. Although I can understand the alterations from a ratio point of view, it should resemble the official Blender icon. It's very noticeably the wrong icon to me and a lot of our community members since it doesn't have the slanted look that the original had.

Some additional context: The discussion surrounding changing it stemmed from someone noticing that .blend icons in the Gitea instance of Blender looked wrong. Gitea uses this project for its material-themed file icons, e.g.:

image

Source: https://projects.blender.org/blender/blender/src/commit/3893dd068438c6ced64b546d74035bf8507a657d/tests/files/diff/blends

We hope you will reconsider merging the icon, or otherwise I would suggest having an -alt version for them to be both available.

@PKief
Copy link
Copy Markdown
Member

PKief commented Dec 11, 2025

Hi @bartvdbraak, thanks for your reply. In general, I agree @lucas-labs as this project is a little bit opionionated. Our goal is not to be as close as possible to the original logo but to provide "Material Design" like way to align all of our icons together. And on top of that we align the icons to a 16x16 grid to improve the visibility on small resolutions. So far this made our project quite popular and successful.

I could read the following statement in your trademark policies:

Modifying the Blender logo is really part of your own artistic freedom, and the Blender Foundation will never act against such tributes. Just don’t expect us to “officially approve” of it, that’s all.

https://www.blender.org/about/logo/#artwork

This would encourage me to say that our project also has its own way to tribute to the blender community. And our adjustment isn't that much different to how the official logo looks like - the icon is still clearly recognizable as the blender logo and we took the creation of the icon fully seriously so that we don't harm the idea of the blender project or community in any way.

Let me know your thoughts on this

@julianeisel
Copy link
Copy Markdown

For comparison...

  • Current:
  • Proposed here:

The current icon distorts and "blows up" the logo quite a bit. That makes it look very cartoony or goofy to me, like a Comic Sans version 👀 This isn't how I'd want the Blender brand to be perceived personally.

So while some tweaking to align to a pixel grid can be fine, I think the Blender community would appreciate a representation that isn't "goofy", and closer to the original.

Not to be dismissive, some Blender people just care a lot :)

@lucas-labs
Copy link
Copy Markdown
Member

image

I've been playing with this one and made a few variations. The first one is the current one. The other 2 are two slightly different variations I came with.

Let me know what you think.

@mcgrathd
Copy link
Copy Markdown
Contributor Author

image I've been playing with this one and made a few variations. The first one is the current one. The other 2 are two slightly different variations I came with.

Let me know what you think.

I am sorry if I misunderstand, but was there a problem with the image that I submitted in the PR? It's not quite clear what is unacceptable with my original modifications.

@lucas-labs
Copy link
Copy Markdown
Member

I am sorry if I misunderstand, but was there a problem with the image that I submitted in the PR? It's not quite clear what is unacceptable with my original modifications.

Hi @mcgrathd! We try to make all of our icons pixel-perfect at 16x16 pixels, which is the size vscode renders all icons in the tree view (with default settings).

image

Your's is the semi-transparent blue-ish on top of the one I labeled blender-3_1 in my previous message, in orange. That's the difference, mine is aligned to a 16x16 grid and uses exactly 2 pixels width lines (also aligned) for the three lines. That makes the icon look less blurry at 16x16 px.

We have a section on pixel-perfect icons in the contribution guidelnes.

@mcgrathd
Copy link
Copy Markdown
Contributor Author

Hi @mcgrathd! We try to make all of our icons pixel-perfect at 16x16 pixels, which is the size vscode renders all icons in the tree view (with default settings).

Your's is the semi-transparent blue-ish on top of the one I labeled blender-3_1 in my previous message, in orange. That's the difference, mine is aligned to a 16x16 grid and uses exactly 2 pixels width lines (also aligned) for the three lines. That makes the icon look less blurry at 16x16 px.

Ah, that makes sense. I just took the exact SVG contents from the logo kit and put it on some (not all) of the grid, and let the logo fall where it may otherwise.

I think this is the heart of the problem though: You want pixel perfect, which aligns great, but isn't our logo. We were asking for the original slanted logo which can never align to the grid at every point due to the design.

Granted that it looks like I could have went down a pixel or two! Thanks for taking the time to explain the problem. 👍

@PKief
Copy link
Copy Markdown
Member

PKief commented Dec 17, 2025

image I've been playing with this one and made a few variations. The first one is the current one. The other 2 are two slightly different variations I came with.

Let me know what you think.

I think the third icon looks a little bit better, I would like that also

image

@julianeisel
Copy link
Copy Markdown

julianeisel commented Dec 17, 2025

I think the 3rd variation (blender-3_1) is a fair enough representation of the original, I think we'd be able to live with that 😜

Although the uppermost "finger" still only partially overlaps a bunch of pixels, so we don't gain much by thickening all that much. I think we can reduce the thickness closer to the original?:
Group(2)

And while we're at it :) Will it really introduce much blurriness to slightly reduce the width of the 2nd finger as well? It would still be mostly opaque:
Group(3)

This way the logo isn't all that distorted at bigger sizes or higher pixel densities like retina displays.

@bartvdbraak
Copy link
Copy Markdown

image

I've been playing with this one and made a few variations. The first one is the current one. The other 2 are two slightly different variations I came with.

Let me know what you think.

@lucas-labs 3_1 looks so much better! Time for a PR? 😊

Copy link
Copy Markdown
Member

@PKief PKief left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @lucas-labs for the updated icons and the efforts! From my perspective it looks in a way where we still match our guidelines and it looks less "goofy" (I absolutely do not prefer that term if it's describing one of our icons, but it seems that it describes the requirement by the blender community). So I think we're good to merge this now :)

@PKief PKief merged commit 8fd8793 into material-extensions:main Jan 13, 2026
5 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

Merge Successful

Thanks for your contribution! 🎉

The changes will be part of the upcoming update on the Marketplace.

@bartvdbraak
Copy link
Copy Markdown

Thank you @lucas-labs @PKief!

As soon as there's a new release on NPM, I'll configure our Gitea instance at Blender to start using that ☺️.

@PKief
Copy link
Copy Markdown
Member

PKief commented Jan 21, 2026

@bartvdbraak FYI a new version has been released with the changes.

https://www.npmjs.com/package/material-icon-theme/v/5.31.0

@bartvdbraak
Copy link
Copy Markdown

@bartvdbraak FYI a new version has been released with the changes.

https://www.npmjs.com/package/material-icon-theme/v/5.31.0

Thanks we'll start to use it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

icons PR with new icons

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants