Question 1

What is ClearLogo?

Accepted Answer

ClearLogo is a logo API that returns a single, clean image for any domain. Unlike generic logo sources, it focuses on presentation: every response is background-aware, auto-cropped, and ratio-fit so logos look consistent inside dashboards, CRMs, company tables, and other product surfaces.

Question 2

Do I need to sign up to try the API?

Accepted Answer

No. You can make anonymous requests to https://api.clearlogo.dev/logo/{domain} right away for low-volume testing — no key required. For production traffic you'll need a browser key or server key from the dashboard.

Question 3

Do I need a backend server to use ClearLogo?

Accepted Answer

No. A browser key lets you embed logo URLs directly in <img> tags from frontend code. Requests are validated by Origin/Referer matching against the allowed domains you configure on the key. Use a server key only when you prefer Authorization: Bearer authentication from your backend.

Question 4

Where do I start?

Accepted Answer

The fastest path: open the playground, paste a few representative domains, and see how the output looks in your UI. Once you're happy, create a production key in the dashboard and swap the URL into your code.

Question 5

What are the best use cases for ClearLogo?

Accepted Answer

ClearLogo is a strong fit wherever logos sit side-by-side and visual consistency matters — company tables and directories, CRM account lists, enrichment UIs, sales tools, and internal dashboards. If you only need a one-off logo behind a server-side cache and presentation consistency isn't a concern, a generic source may be sufficient.

Question 6

What's the difference between a browser key and a server key?

Accepted Answer

A browser key (pk_…) is safe to ship in frontend code and <img> tags. Requests are authenticated by matching the Origin or Referer header against the allowed domains you configure. A server key (sk_…) authenticates via Authorization: Bearer YOUR_KEY from your backend and must never be exposed to the browser.

Question 7

How do I restrict my browser key to specific domains?

Accepted Answer

In the dashboard, open the key's settings, enable Allowed Domains Only, and add your domains one per line. Wildcard notation like *.example.com is supported for subdomains.

Question 8

What happens to requests without a Referer header after I enable domain restrictions?

Accepted Answer

They are blocked. Direct traffic and requests sent with Referrer-Policy: no-referrer or same-origin will fail once domain restrictions are active. Policies that work include strict-origin-when-cross-origin, origin, origin-when-cross-origin, and unsafe-url. You can verify your setup by checking for the Referer header on img.logo.dev requests in your browser's Network tab before enabling restrictions.

Question 9

How do I rotate or replace an API key?

Accepted Answer

Create a new key in the dashboard, update your integration to use it, then delete the old key. If you need an urgent rotation, contact support@clearlogo.dev.

Question 10

What image formats does ClearLogo return?

Accepted Answer

png is the default. You can request webp or jpeg via the format query parameter. When format is omitted, the API content-negotiates from the Accept request header — modern browsers loading via <img> receive WebP automatically.

Question 11

What does "background-aware" output mean?

Accepted Answer

ClearLogo detects whether a brand's logo is designed for a colored or dark background and preserves that background in the response image. This prevents the common problem of transparent logos that look broken on light surfaces.

Question 12

What sizes are available?

Accepted Answer

The size parameter accepts these values: 16, 32, 48, 64, 96, 128, 192, 256, 512, and 1024 pixels. The image is always square. The default is 128 px. Values outside this list are snapped to the nearest allowed size (ties round up).

Question 13

What does the `content` parameter control?

Accepted Answer

It sets how much of the canvas the logo occupies, expressed as a percentage from 50 to 100 (step 5). A lower value adds more padding around the logo; 80 is the default and works well for most product UIs.

Question 14

What does the `theme` parameter do?

Accepted Answer

Setting theme=dark returns the dark-background variant of a logo when one is available. If no dark variant exists, the API falls back to the standard version.

Question 15

What are the rate limits?

Accepted Answer

Limits vary by plan — see the pricing page for details. Per-key usage is returned in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers so you can monitor consumption in real time.

Question 16

What happens when I exceed my rate limit?

Accepted Answer

The API returns HTTP 429 with a Retry-After header indicating how many seconds to wait before retrying. We'll contact you before taking any further action — service is not cut off without warning.

Question 17

How do I check my current usage?

Accepted Answer

Real-time usage is visible in the dashboard. You can also read the X-RateLimit-Remaining header on any API response.

Question 18

A logo isn't showing for a domain — what should I check?

Accepted Answer

Work through this checklist: (1) confirm the domain is a bare hostname with no scheme or path, e.g. github.com not https://github.com/; (2) check that your API key is valid and not expired; (3) if domain restrictions are enabled, verify the Referer header is being sent; (4) check the response status code — 404 means no logo was found for that domain, 401 means an auth problem, 429 means rate limited.

Question 19

The logo for a domain looks wrong or outdated — what can I do?

Accepted Answer

Contact us at support@clearlogo.dev with the domain name and a note about what looks incorrect. We'll review it and update the asset.

Question 20

I'm getting a 401 error — what does that mean?

Accepted Answer

A 401 means the request wasn't authenticated. For browser keys, ensure the token query parameter is included and that the Origin/Referer header matches an allowed domain. For server keys, ensure the Authorization: Bearer YOUR_KEY header is present and the key hasn't been deleted.

Question 21

Logos load in production but not during local development — how do I fix that?

Accepted Answer

Add localhost (or localhost:3000, localhost:5173, etc.) to your key's allowed domains in the dashboard. The API matches against the exact origin, so include the port if your dev server uses a non-standard one. Remove local entries before distributing the key, or create a separate development key.

Question 22

I'm seeing CORS errors in the browser — how do I fix that?

Accepted Answer

The API sets permissive CORS headers, so CORS errors usually indicate a missing or blocked Referer header rather than a true CORS issue. Check your page's Referrer-Policy — policies like no-referrer prevent the Referer header from being sent, which will cause requests to fail when domain restrictions are active. Also check the <img> tag itself: a referrerpolicy="no-referrer" or referrerpolicy="same-origin" attribute on the element overrides the page-level policy and strips Referer from that specific request.

Question 23

What plans are available?

Accepted Answer

ClearLogo offers a free plan for low-volume use and paid plans for production traffic. See the pricing page for the current plan details and request limits.

Question 24

How do I upgrade my plan?

Accepted Answer

Visit the dashboard and select Upgrade from your plan card. You'll be taken to the billing page where you can choose a plan and complete payment.

Question 25

Can I cancel my subscription?

Accepted Answer

Yes. You can cancel at any time from the dashboard. Your plan remains active until the end of the current billing period.

Help & FAQ

Getting Started

API Keys & Authentication

Output & Formatting

Rate Limits & Usage

Troubleshooting

Billing & Plans

Still have a question?