To put a company logo on your site, you can start with three kinds of sources: icon libraries such as Simple Icons and SVGL, logo collections such as VectorLogoZone and Brandfetch, and the official assets published by the brand itself. The right pick depends on the use: a "works with" row and a logo placed on your own product do not carry the same risk.

The rule that prevents most trouble fits in one sentence: a file can be free of copyright while the trademark remains restricted. Simple Icons releases its repository under CC0, but its own disclaimer says that does not automatically cover every icon, and that users must check each brand's terms. Logoforge makes the same point: a free license covers the file, not the brand. Every source below therefore answers two separate questions: what the file license allows, and what the trademark owner allows.

Versions, star counts and quotas were checked on November 6, 2026, on official pages and GitHub repositories. Free plans change, so confirm the current terms before you build a production workflow on one. This is not legal advice: for a high-stakes commercial use, have a lawyer review the page.

What a file license does not cover#

A logo often combines two separate rights. Copyright protects the drawing, curves, colors and composition of the file. Trademark law protects the sign that identifies a company, product or service. A Creative Commons, MIT or CC0 license can let you copy and modify the artwork without giving you permission to use the mark in a way that suggests affiliation.

Three uses usually pass without written permission: reference, commentary and comparison. Showing Stripe's logo in a list of payment integrations, using Figma's mark in an article that compares design tools, or including GitHub in a screenshot of your own app are referential uses. Brandfetch's logo fair use guide puts it plainly: identifying a brand is acceptable; putting someone else's logo on your product or implying a partnership is not.

The uses to avoid are easier to list. Do not use another company's logo as your product logo. Do not put it in an ad that suggests endorsement. Do not recolor it, stretch it, add effects or combine its symbol with your name. Do not place it in a "trusted by" row when no relationship exists.

Brand guidelines can be stricter than general trademark law. Microsoft's Trademark and Brand Guidelines state that its logos, app icons and designs can never be used without an express license. Apple's guidelines for third parties say the Apple logo may not be used on a website, product or promotional material without written permission. In other words, fair use does not override a brand's written rules: the trademark owner can forbid a use that copyright law would otherwise tolerate.

One more nuance: very simple logos may fall below the threshold of originality in some countries and therefore lack copyright protection. Wikimedia Commons hosts files tagged PD-textlogo for that reason, but its copyright rules page notes that trademark is a separate restriction. A logo that is public domain for copyright purposes is not automatically free for trademark purposes.

The sources at a glance#

SourceCoverageVariantsFile licenseAccessPrice
Simple Icons3,400+ iconsMonochrome, CDN colorCC0 repository, per-icon licenses to checkNode package, CDN, SVGFree
SVGL676 logosColor, light/dark, logotypeMIT code, logos are trademarksREST API, SVGFree
VectorLogoZone5,598 files for 1,768 projectsColor, logotype, tileNo blanket license, check each fileSite, CDN, GitHubFree
Font Awesome Freev7 libraryBrand icons, SVG, fontIcons CC BY 4.0, font SIL OFL 1.1, code MITNode package, CDNFree
Brandfetch50M+ brandsLogo, icon, logotype, light/darkTrademarks, API termsAPI, CDNLogo API free up to 1M requests/month
Logoforge1,019 logosIcon, mono, logotype, light/darkCC0 sources or official artwork, MIT toolingJSON, SVG, CLIFree
Wikimedia CommonsVariesSVG, PNG, logotypePer-file license, including PD-textlogoSite, APIFree
Coverage, licenses and quotas checked in November 2026 on official pages. The license column covers the file or the code, not the trademark.

Simple Icons: 3,400+ monochrome icons under CC0#

Simple Icons is the usual starting point for one-color logos. Its GitHub repository says "Over 3400 SVG icons for popular brands", shows 26,200 stars and carries a CC0 1.0 license. Each icon is a 24 × 24 SVG path, which makes it easy to color with currentColor. That format works well for a grayscale logo row, a sidebar or an integrations list.

The license needs a careful read. The repository is CC0, but the DISCLAIMER says that does not mean every icon is also CC0: some carry a different license, and license data can be out of date. The same document asks users to read brand guidelines and check each icon's license in the package data. It also documents a removal channel: a brand can write to [email protected], and icons that no longer meet the contribution criteria are dropped in the major releases shipped roughly twice a year. For a commercial project, do not treat the repository as permission for every icon.

One command adds the package, then a short script writes the SVGs into your public folder. The simple-icons package is tree-shakeable: a bundler such as webpack or Vite keeps only the icons you import.

bash
npm install simple-icons
js
import { siGithub, siFigma, siStripe } from "simple-icons";
import { mkdirSync, writeFileSync } from "node:fs";

mkdirSync("public/logos", { recursive: true });

for (const icon of [siGithub, siFigma, siStripe]) {
  writeFileSync(`public/logos/${icon.slug}.svg`, icon.svg);
  console.log(`${icon.title}: ${icon.license?.type ?? "license not listed"}`);
}

For a React component, skip the intermediate file and render the path directly. The logo stays accessible when you add a label that screen readers can announce.

tsx
import { siGithub } from "simple-icons";

export function GitHubMark(props: React.SVGProps<SVGSVGElement>) {
  return (
    <svg
      role="img"
      aria-label={siGithub.title}
      viewBox="0 0 24 24"
      {...props}
    >
      <path d={siGithub.path} fill="currentColor" />
    </svg>
  );
}

The official CDN lets you skip installation for a prototype: https://cdn.simpleicons.org/github/181717 returns the SVG in the requested color. The color can be a hex value or a CSS keyword, and a third segment sets the color used in dark mode. For a production site, download the file and serve it from your domain: you control the version and avoid a third-party dependency.

The limitation is coverage. Simple Icons offers monochrome marks, not full logos with logotypes. For a colorful partner page, add SVGL, VectorLogoZone or the brand's official assets.

SVGL: 676 color logos with light and dark variants#

SVGL is a color logo library with a GitHub repository at 5,000 stars, an MIT license for the code and 676 logos listed on its home page on November 6, 2026. Each entry can include a light version, a dark version, a logotype and a link to the brand's guidelines. It saves you from hunting each variant separately when a logo row must stay readable in both themes.

The MIT license covers SVGL's code, not the trademarks. The repository warns contributors to make sure they have the right to use a file before submitting it. The API documentation says the service is free, needs no authentication, applies an unspecified rate limit and recommends caching responses. It also asks users not to rebuild the same product from the API.

The REST API accepts a title search and returns the variant URLs. One command is enough to fetch a logo and write it into your project.

bash
curl -s "https://api.svgl.app?search=stripe" | jq '.[0]'
curl -L "https://api.svgl.app/svg/stripe.svg" -o public/logos/stripe.svg

The first call returns an array; jq '.[0]' extracts an object whose title, category and url identify the match, whose route holds either one URL or a light/dark pair, and whose optional wordmark field gives the text version, as documented in the API types. The second returns the SVG optimized with SVGO. If the entry has route.light and route.dark, the two URLs point to separate files: plan for both in your component instead of filtering the logo with CSS.

SVGL fits tech products and common brands. If a logo is missing, the library accepts contributions, but you must supply the SVG and check your rights. A logo added by a contributor is not a legal validation from the brand.

VectorLogoZone: 5,598 files, 1,768 projects, licenses to check#

VectorLogoZone lists 5,598 images for 1,768 companies or projects, with logos that are consistently sized and ready for a README or a credits page. Each brand can have several formats: full logo, logotype, tile, horizontal version. That helps when you want a visually even row without editing every file.

The license has to be checked file by file. The home page says the logos are "free to use", but the FAQ is more careful: the maintainer says he does not own the copyrights or trademarks and that use is "at your own risk". There is no site-wide CC0 license to rely on. Treat each file as a starting point to verify, not as permission for every logo in the collection.

The typical use is an open-source project, an article or a credits page where the logo identifies a tool. The site allows direct linking and offers a CDN, but hosting the file yourself is safer: you avoid a dependency and can pin the version. If the brand publishes guidelines, follow them even when the file comes from VectorLogoZone.

Font Awesome Free: brand icons inside a general icon library#

Font Awesome Free v7 is a general icon library, not a logo bank. It includes brand icons that work as social icons or pictograms inside an interface. Its GitHub repository shows 77,000 stars. The license stacks three regimes: CC BY 4.0 for SVG and JS icons, SIL OFL 1.1 for fonts, MIT for code.

Attribution is embedded in the downloaded files as comments. The license page asks users not to actively remove those comments. If you extract an SVG and clean it with SVGO, make sure you do not strip the attribution: it is a condition of CC BY 4.0. For brand icons, Font Awesome says they remain trademarks of their owners and asks users not to use them "for any purpose except to represent the company, product, or service to which they refer".

Font Awesome is a good fit if the library is already in your project and you want a GitHub, Discord or Slack icon that matches the rest of the UI. It is a poor fit for a colorful customer page with logotypes: coverage is narrower and the result looks like an interface icon, not a brand logo.

Brandfetch: official assets at scale#

Brandfetch indexes 50 million brands and offers several APIs. The Logo API displays logos in an application, with a free fair-use quota of 1,000,000 requests per month and no required attribution (usage guidelines). URLs must be embedded in <img> tags, programmatic fetching of the CDN is refused, and caching requires a custom agreement; throughput is capped at 1,000 requests per 5 minutes per IP and 2,400 per 5 minutes per customer. The Brand API returns a full brand record — logos, colors, fonts, firmographics — from a domain, a ticker, an ISIN or a crypto symbol, with 100 brand fetches offered once; beyond that, it costs $129 per month billed monthly or $99 per month billed yearly for 2,500 brand fetches, with a $0.10 overage per fetch (pricing). The Brand Search API autocompletes brand names in a form, free up to 500,000 requests per month.

This is the right source when you do not know the brands in advance: a company directory, a tool that shows the connected customer's logo, a transaction list or an onboarding flow. The API returns light and dark variants, icons, logotypes and sometimes colors and fonts. The service is commercial, but the free quotas cover a small product or a prototype.

Brandfetch does not transfer the trademark. Its FAQ is explicit: logos belong to their owners, use must follow fair use principles, and if you are unsure, ask for permission or consult a lawyer. An API that hands you a file does not give you the right to use it however you want. For a dynamically displayed logo, plan a readable fallback when the image fails: the brand name in text is often enough.

Logoforge: 1,019 logos for shadcn/ui projects#

Logoforge is a catalogue of SVG logos for developer tools, published by the same publisher as this blog. It lists 1,019 logos in three formats: raw SVG files, typed React components, and shadcn/ui components added in one command. The project is free and open source, with MIT-licensed tooling (GitHub), and it also ships an MCP server for AI agents (docs).

The credits and licenses page names the origin of each file: 285 icons from Simple Icons, 719 from gilbarbara/logos, also published under CC0 1.0, 6 from Wikimedia Commons for public-domain logos, and 6 official artwork files marked trademark. Simple Icons files published under another license are excluded. Each logo page names the source and the file license, and removal requests are handled within 72 hours.

In a Next.js project that already runs shadcn/ui, one command writes the component into components/logos:

bash
npx shadcn@latest add @logoforge/stripe
tsx
import { StripeLogo } from "@/components/logos/stripe";

export function PaymentBadge() {
  return <StripeLogo variant="mono" className="h-6 w-auto" />;
}

The catalogue also exposes a static JSON API: https://logoforge.terravidhal.me/api/logos/stripe.json returns the slug, categories, color, page, SVG variants and installation command. As with any other source, the file license does not settle trademark rights: Logoforge links to a brand's public guidelines and handles removal requests within 72 hours.

Logoforge fits a landing page, documentation or an integrations page that lists developer-tool logos. It is not a general-purpose brand bank: if your site covers banks, media or consumer brands, Brandfetch or the official press kits are a better fit. If you are building the page itself, our 10-minute shadcn/ui landing page guide covers the section layout, and our shadcn/ui vs Mantine vs Chakra UI comparison helps if you are still choosing the component library.

A five-step workflow#

Step one is to define the use before downloading anything. Write it down: does the logo identify a brand in informative content, show a real integration, or decorate your own product? If the answer is "decorate", stop. You probably do not need the logo, and you are taking an unnecessary risk.

Step two is to read the brand guidelines. Search for "brand guidelines", "press kit" or "trademark guidelines" on the official site. Google centralizes its rules in its Brand Resource Center, Apple and Microsoft publish detailed pages, and GitHub has a Brand Toolkit. These pages often state whether the logo is allowed, in which colors, at what minimum size and with which trademark notice.

Step three is to pick the source that documents its license. For a monochrome icon, Simple Icons. For a color logo with a dark variant, SVGL. For a logotype missing from the libraries, VectorLogoZone or Wikimedia Commons. For large-scale dynamic display, Brandfetch. For a shadcn/ui project, Logoforge. Avoid sites that offer a download button with no license, no source and no contact page: you cannot tell what you are downloading.

Step four is to pin the file and document its origin. Create a LICENSES.md file or a comment in the component with the source URL, the license and the download date. Optimize the SVG with SVGO, but keep the viewBox attribute and the accessibility attributes.

bash
npx svgo public/logos/*.svg --multipass

Step five is to integrate the logo correctly. A decorative SVG should have aria-hidden="true". An SVG that carries information needs role="img" and an aria-label or a <title>. Avoid fixed pixel width and height; let the viewBox attribute and a height class do the work. For dark mode, use currentColor when the logo is monochrome, or load the dark variant when one exists.

tsx
export function BrandMark({
  src,
  name,
  href,
}: {
  src: string;
  name: string;
  href: string;
}) {
  return (
    <a href={href} className="inline-flex items-center gap-2">
      <img src={src} alt="" width={24} height={24} loading="lazy" />
      <span>{name}</span>
    </a>
  );
}

Six mistakes that invite a takedown request#

The first mistake is to confuse "SVG found on Google Images" with "usable logo". A file with no explicit license is not in the public domain. Sites that aggregate logos without naming their source do not protect you: if the brand asks for removal, you are the one who has to answer.

The second mistake is to treat a code license as a trademark license. A GitHub repository under MIT, Apache-2.0 or CC0 can contain third-party logos. The repository license covers the code or the selection, not the marks shown. Read the notice, not just the badge at the top of the README.

The third mistake is to use an outdated logo. Brands change their marks, colors and logotypes. A logo downloaded three years ago may be wrong today. Check the official page or the last update date before publishing. For a dynamic logo, add a fallback and an alert when the image no longer matches the name.

The fourth mistake is to modify the logo. Recoloring it, adding an outline, tilting the symbol or combining it with your own mark can violate the guidelines and, in some cases, trademark law. If you need a monochrome version, use the mono variant provided by the source or currentColor when it is allowed, not a CSS filter that distorts the logo.

The fifth mistake is to forget attribution. CC0 does not require it; CC BY 4.0 does. Font Awesome embeds attribution in its files, but aggressive cleaning can remove it. For a CC BY library, keep the notice in your credits or in the code. For brand logos, the guidelines sometimes require a trademark notice even when the file is free.

The sixth mistake is to assume a "trusted by" row is harmless. Showing a company logo without a real relationship can mislead visitors, and brands do enforce this. If you have no customers, use a quote, a verifiable number or a project example. A logo without a real relationship invites a complaint from the brand instead of building trust.

Our pick for each profile#

Frequently asked questions#

Frequently asked questions

Can I use a brand logo on my site without permission?

It depends on the use and the guidelines. Identifying a brand, reviewing a product or showing a real integration is often accepted. Decorating your product, suggesting a partnership or selling a service around the logo requires permission. Microsoft and Apple prohibit use of their logos without an express license, even in some referential contexts.

Is Simple Icons really free?

The repository is under CC0 1.0, but the documentation says not every icon is necessarily CC0 and that license data can be out of date. Check the icon's license in the package data and the brand guidelines. The file license does not settle trademark rights.

What is the difference between VectorLogoZone and Brandfetch?

VectorLogoZone is a static collection of 5,598 files for 1,768 projects, with a license to verify case by case. Brandfetch is a commercial platform with 50 million brands, APIs and free quotas. VectorLogoZone fits a specific logo in an open-source project; Brandfetch fits large-scale dynamic display.

Does Font Awesome Free require attribution?

Yes, CC BY 4.0 requires attribution for SVG and JS icons. Downloaded files already contain attribution comments, and the license page asks users not to actively remove them. If you clean the SVG, keep the notice or add it to your credits.

Can I use a CC0 logo as my own product logo?

No, not automatically. CC0 covers copyright in the file, not trademark rights. Using another company's logo as your product logo can confuse users about origin and violate trademark law. For your own logo, start from an original design or an icon set whose license allows that use.

What should I do if a brand asks me to remove its logo?

Remove it quickly, keep a record of the request, and replace it with the brand name in text if the use remains informative. Libraries such as Logoforge provide a removal process; other sources may not. Keep the source and license details so you can understand what happened.

Sources#

Official pages, GitHub repositories and pricing pages checked on November 6, 2026. Star counts and quotas are those displayed on that date.