Logo requirements

Inboxes show your logo as a small circle next to your name. They need it in a very specific file format, SVG Tiny P/S. You don't need to create that file: give us your logo and we prepare it.

What to give us#

Any of these works:

• An SVG file of your logo (best). Ask your designer or check your brand guidelines.
• A link to your logo file online.
• The logo on your website. We look for it automatically; you just confirm.

The file can be up to 512 KB. If you only have a PNG or JPG, we'll tell you; a vector version (SVG, or a PDF/EPS from your designer) gives the best result.

What makes a logo look good in the inbox#

• Square. The logo is shown in a circle, so a square layout with some breathing room around the mark works best.
• A solid background. Use your brand color or white behind the mark, rather than a transparent background.
• Simple and bold. It's shown small. A symbol or monogram often reads better than a long wordmark.
• The same as your trademark if you want the blue checkmark. See Trademarks.

What we do to your logo#

1. We keep your original file exactly as you gave it, separately.
2. We create an inbox-ready copy in SVG Tiny P/S: a square canvas, a title with your company name, and without the features the format doesn't allow (scripts, embedded images, animations, external links, some effects).
3. We compare the two visually and list every change we made, flagging any that alter how the logo looks.
4. You review them side by side and approve the version that will be used.

Some advanced design effects can't be carried over exactly. When that happens, we tell you, and you can provide a simpler version.

Approval#

In the setup phase, you approve the exact inbox-ready file. Nothing is sent to the certificate issuer until you do. If you change your logo later, we can prepare a new version and reissue your certificate.

For developers#

• PUT /v1/applications/{id}/logo with { "svg": "…" }, { "url": "https://…" } or { "use_discovered": true }.
• GET /v1/applications/{id}/logo returns status, analysis (compliance issues), changes (with a lossy flag), visual_diff (identical, minor, significant) and URLs for the original, converted and PNG previews.
• POST /v1/applications/{id}/logo/approve with converted_sha256 approves exactly the reviewed file (paid step).
• Uploaded SVGs are size-limited, never rendered inline, and served with a restrictive content security policy; links are fetched through a protected fetcher.