<img> tag. Brandfetch starts from the JSON brand profile.
Logo.dev vs Brandfetch
Logo.dev fits when the logo image is the main thing you need. The publishable key is safe in client code, so the browser loads the logo from the URL and your code parses nothing. When you need more, Brand returns the full profile from your server.
Brandfetch fits when you need data that Logo.dev does not return, such as brand fonts or company details. It also fits when you need SVG files from the CDN.
Map Brandfetch products to Logo.dev
Logo images move to the Logo.dev CDN. Brand data and search move to the Logo.dev API.Get your API keys
Your dashboard has a publishable key for the Logo.dev CDN and a secret key for the Logo.dev API. Every plan includes both.
Migrate logo images
Both CDNs build the logo from a URL. Change the host, change the credential, and rename the parameters:
Add
format=png or format=webp to every URL. The Logo.dev CDN returns JPG by default, and JPG has no transparency.
Logo.dev’s theme names the background you show the logo on, so theme=dark keeps a logo visible on a dark background. Set it from your own background color. Do not copy the Brandfetch value.
The Logo.dev CDN returns one logo per company. For the wide lockup that Brandfetch calls the logo type, call GET /v2/brands/brandmark from your server.
Every Logo.dev CDN parameter lists the full set.
Migrate brand data
Both Brand APIs return one JSON profile per brand and take a bearer token. Send your Logo.dev secret key instead of the Brandfetch key:ticker, isin, crypto, or name in place of domain.
The Logo.dev profile has the name, description, colors, socials, logo, brandmark, and social banners. It does not have fonts, company size, or industry. If you use those Brandfetch fields, compare the Brand response with your needs before you move that call.
Migrate search
Change the Brandfetch search path to theq parameter, and send your secret key: