> ## 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.

# Clearbit Logo API Alternative & Migration Guide

> Clearbit's Logo API shut down on December 8, 2025. Logo.dev is the drop-in replacement from the same team — migrate your logo.clearbit.com URLs in minutes.

<Warning>
  **Clearbit Logo API shut down on December 8, 2025.** If your app still uses
  `logo.clearbit.com`, it no longer works. Logo.dev is the official migration
  path recommended by Clearbit / HubSpot.
</Warning>

This guide will help you replace Clearbit's Logo API with Logo.dev for displaying company logos on your website or app. Most migrations only take a few minutes to change your **Base URL** and add a Logo.dev **Publishable Key** for authentication. Once you migrate, you can access the additional features Logo.dev provides such as new image parameters and alternate lookup methods.

## Why Logo.dev?

**We're the same team that originally built the Clearbit Logo API** and are the recommended migration partner by Clearbit / Hubspot.

Logo.dev serves tens of millions of logo images daily with a focus and dedication to quality. Our goal is to be the reliable platform that millions can use for free, with upgraded paid features that sustain the service long term. That way, you never have to migrate to another service again.

If your logos broke when Clearbit shut down, you can restore them in minutes. Migrate now and join the tens of thousands of developers using Logo.dev today.

## Migrate your website or app

<Steps>
  <Step title="Update your Base URL">
    Logo.dev is a one-to-one replacement for the Clearbit Logo API so all your parameters will continue to work as you expect. After replacing the **Base URL**, your images will not be returned until you authenticate them.

    ```bash Clearbit Base URL theme={null}
    https://logo.clearbit.com/
    ```

    ```bash Logo.dev Base URL theme={null}
    https://img.logo.dev/
    ```
  </Step>

  <Step title="Create an account and add your Publishable Key">
    To use Logo.dev, you'll need to [create an account](https://www.logo.dev/signup) and get your **Publishable Key** from the dashboard.

    ```bash Logo.dev Publishable Key theme={null}
    LOGO_DEV_PUBLISHABLE_KEY=pk_xxxxxxxxxxxx
    ```

    For all integrations, it's as simple as adding the `token` parameter and passing your **Publishable Key**.

    ```bash Logo.dev Authenticated URL theme={null}
    https://img.logo.dev/:domain?token=LOGO_DEV_PUBLISHABLE_KEY
    ```

    Here are examples of how to add your authentication in different programming languages:

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

      ```jsx React theme={null}
      function CompanyLogo({ domain }) {
        return (
          <img
            src={`https://img.logo.dev/${domain}?token=LOGO_DEV_PUBLISHABLE_KEY`}
            alt={`${domain} logo`}
          />
        );
      }
      ```

      ```tsx Next.js theme={null}
      // Add img.logo.dev to your next.config.js:
      // module.exports = {
      //   images: {
      //     remotePatterns: [
      //       {
      //         protocol: 'https',
      //         hostname: 'img.logo.dev',
      //       },
      //     ],
      //   },
      // };

      import Image from 'next/image';

      function CompanyLogo({ domain }: { domain: string }) {
        return (
          <Image
            src={`https://img.logo.dev/${domain}?token=${process.env.NEXT_PUBLIC_LOGO_DEV_PUBLISHABLE_KEY}`}
            alt={`${domain} logo`}
            width={128}
            height={128}
          />
        );
      }
      ```

      ```vue Vue theme={null}
      <template>
        <img
          :src="`https://img.logo.dev/${domain}?token=LOGO_DEV_PUBLISHABLE_KEY`"
          :alt="`${domain} logo`"
        />
      </template>

      <script>
      export default {
        props: ['domain']
      }
      </script>
      ```

      ```python Python theme={null}
      import requests

      def get_company_logo(domain):
          url = f"https://img.logo.dev/{domain}?token=LOGO_DEV_PUBLISHABLE_KEY"
          response = requests.get(url)
          return response.content
      ```

      ```ruby Ruby theme={null}
      require 'net/http'

      def get_company_logo(domain)
        uri = URI("https://img.logo.dev/#{domain}?token=LOGO_DEV_PUBLISHABLE_KEY")
        Net::HTTP.get(uri)
      end
      ```

      ```php PHP theme={null}
      function getCompanyLogo($domain) {
          $url = "https://img.logo.dev/{$domain}?token=LOGO_DEV_PUBLISHABLE_KEY";
          return file_get_contents($url);
      }
      ```

      ```kotlin Android (Kotlin) theme={null}
      import com.squareup.picasso.Picasso

      fun loadCompanyLogo(domain: String, imageView: ImageView) {
          val url = "https://img.logo.dev/$domain?token=LOGO_DEV_PUBLISHABLE_KEY"
          Picasso.get()
              .load(url)
              .placeholder(R.drawable.logo_placeholder)
              .into(imageView)
      }

      // Using Coil (modern Android image loading)
      imageView.load("https://img.logo.dev/$domain?token=LOGO_DEV_PUBLISHABLE_KEY") {
          placeholder(R.drawable.logo_placeholder)
          error(R.drawable.logo_error)
      }
      ```

      ```swift Swift (iOS) theme={null}
      import SwiftUI

      struct CompanyLogo: View {
          let domain: String

          var body: some View {
              AsyncImage(url: URL(string: "https://img.logo.dev/\(domain)?token=LOGO_DEV_PUBLISHABLE_KEY")) { image in
                  image
                      .resizable()
                      .aspectRatio(contentMode: .fit)
              } placeholder: {
                  ProgressView()
              }
              .frame(width: 128, height: 128)
          }
      }

      // Using URLSession for direct download
      func downloadCompanyLogo(domain: String) async throws -> Data {
          let url = URL(string: "https://img.logo.dev/\(domain)?token=LOGO_DEV_PUBLISHABLE_KEY")!
          let (data, _) = try await URLSession.shared.data(from: url)
          return data
      }
      ```
    </CodeGroup>

    Learn more about how to get your [API key](/docs/platform/api-keys).
  </Step>

  <Step title="Update your Attribution Link">
    On the free tier, commercial use requires attribution back to Logo.dev wherever you display logos; personal projects don't need it. Skip attribution entirely by [upgrading to any paid plan](https://www.logo.dev/pricing).

    ```html Logo.dev Attribution Link theme={null}
    <a href="https://logo.dev" title="Logo API">Logos provided by Logo.dev</a>
    ```

    Attribution links must be:

    * On a production site.
    * Publicly accessible.
    * Be followable by search engines.

    Learn more about how to [add your attribution link](/docs/platform/attribution).
  </Step>

  <Step title="Test and deploy">
    Before deploying to production, test that logos are displaying correctly:

    * Verify logos match expected companies
    * Check image quality and resolution
    * There are no remaining references to `logo.clearbit.com`

    Any low-quality or incorrect logos can be fixed within 24 hours by [reporting them here](https://www.logo.dev/update). Our team actively maintains the logo database with daily updates.
  </Step>
</Steps>

<Note>
  Need help migrating or require custom features? Contact
  [sales@logo.dev](mailto:sales@logo.dev) for personalized migration assistance,
  enterprise features, or volume pricing. We're here to ensure a smooth
  transition from Clearbit.
</Note>

## Go further

This guide covers the essentials to get you migrated from Clearbit. Once you've made the switch, you can start leveraging Logo.dev's new features that go beyond what Clearbit offered:

* **[Theme variants](/docs/logo-images/get#theme)** for dark and light mode optimized logos
* **[Stock ticker lookup](/docs/logo-images/ticker)** for companies by stock symbol like `AAPL`, `NVDA`, or `META`
* **[Crypto lookup](/docs/logo-images/crypto)** for cryptocurrencies by symbol like `BTC`, `ETH`, or `USDT`
* **[Name lookup](/docs/logo-images/name)** for brand logos when you only have company names, not domains
* **[Brand Search](/docs/brand-search/introduction)** for finding companies by name when you don't know their domain

## Coming from a different logo or favicon API?

Reference docs for other logo and favicon services, and how to switch to Logo.dev:

<CardGroup cols={2}>
  <Card title="Clearbit Logo API" href="/docs/clearbit-logo-docs">
    The deprecated `logo.clearbit.com` endpoint and its parameters.
  </Card>

  <Card title="Google Favicon API" href="/docs/google-favicon-api">
    The unofficial `google.com/s2/favicons` endpoint and its `sz` sizes.
  </Card>

  <Card title="DuckDuckGo Favicon API" href="/docs/duckduckgo-favicon-api">
    The `icons.duckduckgo.com` service: ICO only, no sizing.
  </Card>

  <Card title="Fey Logos" href="/docs/fey-logos">
    The shut-down Fey vector logo library and what replaced it.
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="Will my existing parameters still work?">
    Yes. Parameters like `size`, `format`, and `greyscale` work the same in
    Logo.dev, with the addition of an API token for authentication.
  </Accordion>

  {" "}

  <Accordion title="What's the signup and authentication process for Logo.dev?">
    Sign up takes only a few minutes. Once you create an account you will receive
    an API token that works immediately, with no credit card required for the free
    tier.
  </Accordion>

  {" "}

  <Accordion title="Do I need an API key to use Logo.dev?">
    Yes. Unlike Clearbit's free endpoint, Logo.dev requires a token to monitor
    usage and provide consistent production-level performance.
  </Accordion>

  {" "}

  <Accordion title="What fallback options are available if a logo is not found?">
    Logo.dev provides monograms by default. You can also request `404` responses
    if you prefer to handle your own fallbacks.
  </Accordion>

  {" "}

  <Accordion title="Does Logo.dev support high-DPI screens and multiple formats?">
    Yes. Logos are optimized for high-resolution displays and are available in
    `PNG` and `WebP` formats.
  </Accordion>

  {" "}

  <Accordion title="Does Logo.dev offer a REST API beyond logo retrieval?">
    Yes. The [Brand API](/docs/brand/introduction), on every plan and metered in
    credits, returns a domain's full brand profile: name, description, brand
    colors, social profiles, the logo, the brandmark, and social banner images.
  </Accordion>

  {" "}

  <Accordion title="How much work is required to migrate from Clearbit?">
    Most migrations take less than an hour. Developers only need to replace
    endpoints with Logo.dev URLs, add tokens, and test before deployment.
  </Accordion>

  {" "}

  <Accordion title="Can I test Logo.dev before migrating?">
    Yes. You can sign up for a free account, test with your own domains, and run
    Logo.dev alongside Clearbit during migration.
  </Accordion>

  {" "}

  <Accordion title="Do you support all the domains Clearbit had?">
    Yes. Logo.dev covers all domains Clearbit supported, with frequent updates and
    the ability to request missing logos.
  </Accordion>

  {" "}

  <Accordion title="Is Logo.dev more expensive than Clearbit?">
    No. Logo.dev offers a free tier for testing and affordable paid plans that are
    simpler and more predictable than Clearbit's enterprise pricing.
  </Accordion>

  {" "}

  <Accordion title="How reliable is Logo.dev compared to Clearbit's free API?">
    Logo.dev is built for production use with a global CDN, caching, and monitored
    uptime, while Clearbit's free service was limited and is being discontinued.
  </Accordion>

  {" "}

  <Accordion title="Can I use Logo.dev directly in image tags?">
    Yes. You can embed a Logo.dev URL with your token in an `<img>` tag and it
    will render instantly without extra processing.
  </Accordion>

  {" "}

  <Accordion title="Are there rate limits with Logo.dev?">
    Yes. Each plan has [defined usage limits](https://logo.dev/pricing), and
    higher tiers provide additional capacity for production workloads.
  </Accordion>

  {" "}

  <Accordion title="How quickly are new logos added?">
    New logos are indexed and refreshed frequently to ensure they remain accurate
    and up to date.
  </Accordion>

  {" "}

  <Accordion title="Can I use Logo.dev in commercial applications?">
    Yes. Logo.dev can be used in both internal tools and customer-facing apps.
    Paid plans remove attribution requirements.
  </Accordion>

  <Accordion title="How do I contact support?">
    Email [support@logo.dev](mailto:support@logo.dev) for help with migration, integration, or troubleshooting.
  </Accordion>
</AccordionGroup>