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

# Attribution requirements

> Logo.dev attribution requirements: commercial use on the free plan needs a link back, personal projects don't. Placement rules and implementation.

<Note>
  On the free plan, commercial use requires attribution; personal projects
  don't need it. Upgrade to any [paid plan](https://www.logo.dev/pricing) to
  remove the requirement entirely.
</Note>

## Who needs attribution

* **Commercial projects on the free plan:** yes, a visible link back to Logo.dev.
* **Personal projects on the free plan:** no.
* **Any paid plan:** no.

## What counts as commercial

If a company or organization owns the project, or the project makes (or intends to make) money, it's commercial. It belongs to you as an individual and earns nothing? It's personal.

**Commercial:**

* Products and sites that charge users, run ads, or sell anything
* Startups, including pre-launch and pre-revenue
* Internal tools at a company: dashboards, CRMs, back-office apps
* Client and agency work
* Projects run by an organization, including nonprofits

**Personal:**

* Hobby and side projects with no revenue
* Learning, tutorials, and classroom projects
* Portfolios and personal sites
* Open-source projects you maintain as an individual

Still unsure? [Ask us](mailto:support@logo.dev). Edge cases exist, and we're reasonable about them.

## How attribution works

The link must meet three conditions for verification to pass:

* On your **production site**, not staging or localhost.
* **Publicly accessible** and viewable in a browser.
* **Passing referrer data** (remove any `noreferrer` attributes).

## Implementation

Add this link on any page displaying Logo.dev logos:

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

### Example implementation

```html theme={null}
<div class="customer-logos">
  <img
    src="https://img.logo.dev/apple.com?token=LOGO_DEV_PUBLISHABLE_KEY"
    alt="Apple"
  />
  <img
    src="https://img.logo.dev/google.com?token=LOGO_DEV_PUBLISHABLE_KEY"
    alt="Google"
  />
  <img
    src="https://img.logo.dev/microsoft.com?token=LOGO_DEV_PUBLISHABLE_KEY"
    alt="Microsoft"
  />
</div>
<p class="attribution">
  <a href="https://logo.dev">Logos provided by Logo.dev</a>
</p>
```

## Placement options

Place attribution where users can see it:

* **Near logo displays** - Directly below or beside logo grids
* **In page footer** - With other credits and links
* **On about pages** - For apps behind authentication

## Development workflow

Your API key works immediately for development and testing on localhost or staging environments. Attribution verification only happens when your production site goes live.

1. Sign up for a free account at [logo.dev/signup](https://www.logo.dev/signup)
2. Get your API key from the [dashboard](https://www.logo.dev/dashboard)
3. Start building. The API works right away
4. If you're launching a commercial project on the free Community plan, add attribution to your production site
5. [Submit the public URL for verification](https://www.logo.dev/dashboard/billing?section=attribution#attribution)
6. Check the same dashboard task for the result. If verification fails, fix the issue shown there and submit the URL again

<Note>
  You won't be blocked from using the API while developing on localhost.
  Personal projects and paid plans do not need to complete this task.
</Note>

## FAQs

<AccordionGroup>
  <Accordion title="Do personal projects need attribution?">
    No. Only commercial use on the free plan requires the link. If you're not sure whether your project counts as commercial, [ask us](mailto:support@logo.dev).
  </Accordion>

  <Accordion title="What if my app is behind a login?">
    Add attribution to your public marketing site as well, either in the footer or about page. The attribution must be on a publicly accessible page.
  </Accordion>

  <Accordion title="What about native mobile apps?">
    Include the attribution link on your app's website or in your app store
    listing description.
  </Accordion>

  <Accordion title="Can I use localhost during development?">
    Yes. Your API key works immediately on localhost and staging. Attribution verification only applies to your production domain when you launch.
  </Accordion>

  <Accordion title="What if my attribution link isn't being accepted?">
    Open the [attribution task in your dashboard](https://www.logo.dev/dashboard/billing?section=attribution#attribution), fix the issue shown for your latest check, and submit the URL again. Review the requirements above if it still fails. If a correct, publicly accessible link still cannot be verified after another check, [contact support](mailto:support@logo.dev) so we can investigate.
  </Accordion>
</AccordionGroup>