Option to
manually upload images,
select default available logos,
search web,
to choose unique logos/icons for tokens.
Option to
manually upload images,
select default available logos,
search web,
to choose unique logos/icons for tokens.
Hello Bitwarden Community, Today, we are in 27 February 2025.
I won’t write a lengthy post describing all the past attempts to put icons or other stuff for authenticator, but allow me to just say that it would be interesting if you guys started doing so. (I’m talking about Bitwarden Authenticator App Icons after you add TOTP verification tokens in the Bitwarden Authenticator App) .
If you guys feel the same way as me, the Bitwarden Community, or even the devs, let me know what you think about this.
Thank you very much and let me know about an update for this feature request. I’m down to listen to all opinions/point of views/future dev updates on this matter.
Have a great day,
Vlad Neamtu
if the authenticator cant catch the logo it should have a library to choose the logo from same as ente auth screenshot here
@umbrarix I moved your post into this existing feature request to the same topic.
I would love to see this implemented. I’m not sure how the authenticator is written, but if any JS/TS work is needed, I am willing to lend a hand.
I was going to ask for the same feature.
Authy (Twilio) is the app I was using until now: I guess it finds an image automatically with Google images, but once you edit the account’s logo, it opens a view where many search results you can select from. Works well 9/10
Here’s an API for this. There are others as well. Some may even be free.
Logo API - API Ninjas
There are 3 other feature suggestions mentioning this feature, but I am posting this here with a proposed super easy solution. You don’t have to roll your own. This is a common need for apps, so it’s an API now
tags: logo, icon, icons, favicon
Alternatives
Logo API Tool | Find & Embed Company Logos for Free | Clearbit
Logo API - Add Company Logos to Any Website in Seconds | Logo.dev
Logo API for Company Logos, Stocks and Brands - LogoKit
Many Bitwarden users would not be comfortable with having all web domains stored in their authenticator leaked to a third party.
Then how does every other Authenticator app on god’s earth provide this without raising any ire from their customers?
@grb Stop negging the idea trying to make people give up on a good idea before it’s had a chance to even be thought about. That should not be your first thought, EVER. Learn to adapt the idea to fit the concerns.
There are many options for making this work: caching, masking, etc. Just think before negging
@Grb’s concern is on-point, given that it is called out in Bitwarden’s existing documentation for their website icons.
My question for you, @AMDphreak, is why you feel it better to add a new third-party icon repository instead of leveraging within Authenticator, the one Bitwarden has already built for Password Manager?
@AMDphreak, I merged your feature request into an existing one for the same idea. We prefer one thread per idea as it consolidates votes.
My question for you, @AMDphreak, is why you feel it ebtter to add a new third-party icon repository
@DenBesten I don’t. I didn’t know they even had one internally. If they already have it, why aren’t they using it? If it’s not complete, why wouldn’t they subscribe to an external one to populate missing data?
@AMDphreak, I merged your feature request …
I can see that. But now, the old topic with all of the suggested links will be deleted in 4 days. Think maybe those links are valuable. EDIT: Oh…the post/comments were replicated here as comments. That’s unexpected.
Most likely because Authenticator is a comparatively young, niche product that makes them no money, whereas their flagship product, Password Manager, gets the lion’s share of development effort because it is what brings home the bacon.
That said, now that TOTP entries can sync from Password Manager to Authenticator (new in recent months), it certainly seems like a reasonable first step for at least those icons to sync along with the other relevant bits of the vault entry. Followed by integrating the existing icon code from PM into Authenticator to fill out the “local” entries.