> ## Documentation Index
> Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Logo.dev?

> Learn how the Logo.dev company logo API works: one image URL per logo, plus REST APIs for search, brand assets, and company data.

Logo.dev is a company logo API. You build an image URL from a domain, and the logo comes back ready to render:

```html theme={null}
<img src="https://img.logo.dev/stripe.com?token=LOGO_DEV_PUBLISHABLE_KEY" alt="Stripe logo" />
```

That one URL is the whole integration. Behind it sits a database of 18M+ companies served from a global CDN.

## How it works

The image API reads a company identifier from the URL path and returns the right logo. `img.logo.dev/stripe.com` resolves the domain, and [ticker](/docs/logo-images/ticker), [crypto](/docs/logo-images/crypto), [ISIN](/docs/logo-images/isin), and [name](/docs/logo-images/name) lookups work the same way. Query parameters control `size`, `format`, and `theme`, and a [publishable key](/docs/platform/api-keys) in the `token` parameter makes the URL safe to ship in client code.

When Logo.dev doesn't have a company's logo, the URL returns a generated monogram instead of a broken image (see [fallback images](/docs/logo-images/introduction#fallback-images)). When a company rebrands, the same URL serves the new mark, so there is nothing on your side to update.

For data beyond the logo itself, REST endpoints on `api.logo.dev` take a [secret key](/docs/platform/api-keys) on the server.

## The APIs

* **[Logo API](/docs/logo-images/introduction)**: a logo for any domain, stock ticker, crypto symbol, ISIN, or company name, as a plain image URL.
* **[Search API](/docs/brand-search/introduction)**: turn a company name into its domain and logo, built for autocompletes.
* **[Brand API](/docs/brand/introduction)**: a company's full brand kit, including wide brandmarks, social banners, and brand colors.
* **[Transaction API](/docs/transaction/introduction)**: match messy transaction strings to merchants and their logos.

## When to use it

Anywhere your product shows other companies. The most common starting points:

* **[Transaction feeds](/docs/use-cases/transaction-logos)**: merchant logos next to charges, the way banking apps do it.
* **[CRM records](/docs/use-cases/crm-logos)** and **[onboarding](/docs/use-cases/onboarding-personalization)**: account lists and signups that brand themselves.
* **[Logo walls](/docs/use-cases/customer-logo-wall)**: customer and integration grids without collecting a single SVG.

Browse every pattern, each with a live demo, in [Use cases](/docs/use-cases/introduction).

## Next steps

<CardGroup cols={2}>
  <Card title="Core concepts" icon="book-open" href="/docs/concepts">
    What the terms mean: company logo vs favicon, brandmark, keys, and the APIs.
  </Card>

  <Card title="Quickstart" icon="bolt" href="/docs/quickstart">
    Display your first logo from a plain image URL in under a minute.
  </Card>

  <Card title="Use cases" icon="grip" href="/docs/use-cases/introduction">
    See live demos of logo walls, autocompletes, and transaction feeds.
  </Card>
</CardGroup>