# What developers should actually care about in a company logo API

> Most logo APIs solve retrieval. The harder problem is presentation: dashboards, CRMs, and account lists stay visually consistent only when every logo arrives background-aware, auto-cropped, and ratio-fit.

## The four things that actually matter

- **Background handling** — when a brand background exists, the output should respect it.
- **Whitespace and crop** — logos should not waste space or feel off-center.
- **Ratio consistency** — one UI slot should not produce a different visual weight for every brand.
- **Integration path** — browser apps need a flow that works without forcing a server into the loop.

## Where ClearLogo is opinionated

ClearLogo prioritizes usable output and a browser-friendly public-key flow, making it a strong fit for dashboards, CRMs, enrichment tools, and internal product surfaces.

### Example request

```
GET https://api.clearlogo.dev/logo/example.com?size=128&content=80
```

```html
<img
  src="https://api.clearlogo.dev/logo/example.com?token=YOUR_BROWSER_KEY"
  alt="Example company logo"
/>
```

## Best fit use cases

- Company tables and directories
- CRM and sales tooling
- Account lists inside dashboards
- Browser apps that need logo URLs without a custom signing service

## FAQ

### What does "background-aware" output mean?

ClearLogo detects whether a brand's logo expects a colored or dark background and preserves that background in the response — instead of always returning a transparent PNG that may look broken on light surfaces.

### Do I need a backend to use ClearLogo?

No. A browser key authorizes requests via `Origin`/`Referer` matching, so you can drop URLs directly into `<img>` tags. Use a server key only for bearer-token authentication.

### What logo formats does ClearLogo return?

PNG by default; `webp` and `jpeg` via the `format` parameter or `Accept` header. Modern browsers receive WebP automatically.

### When should I pick ClearLogo over a generic logo source?

When logos sit beside each other in a UI slot — dashboards, CRMs, account lists, enrichment surfaces — ratio-fit and background handling are the differentiators.