SpeechifyAI brand resources.

Everything you need to represent SpeechifyAI correctly — logos, colors, type, the waveform motif, and how we write. Assets on this page are free to use when covering or integrating with SpeechifyAI.

02 — COLOR

Strictly monochrome

White and ink do everything, with a small gray scale for text and borders. The only "accent" is ink — primary buttons are ink, never colored. These are the exact design tokens the speechify.ai site ships. Click any swatch to copy its hex.

There is no color in the system — no colored buttons, headings, or backgrounds. Hierarchy and emphasis come from the gray scale and weight alone.

03 — TYPOGRAPHY

One family: ABC Diatype

ABC Diatype drives every role — display, body, and technical labels. Hierarchy comes from weight and tracking, not from mixing families.

Voice AI indistinguishable
from humans.
Aa
Thin · 100
Aa
Light · 300
Aa
Regular · 400
Aa
Medium · 500
Aa
Bold · 700
Display
All models, one API.

Headlines and heroes. Regular (400), tight tracking (about -0.03em), sentence case, often ending in a period.

Body / UI
Access every model through the same endpoint, with streaming and emotion control.

Paragraphs, UI labels, and controls. Regular and Medium, normal tracking, comfortable line height.

Technical / mono role
model="simba-3.2" · <300ms · $0.07/min

Eyebrows, metrics, model IDs, and code — a brand signal, used liberally. Uppercase eyebrows with wide tracking.

ABC Diatype is a licensed typeface and is not distributed. Third parties should fall back to a system sans-serif (the CSS stack is ui-sans-serif, system-ui, sans-serif), never a lookalike font.

04 — MOTIF

The waveform

Our only recurring graphic is a thin, monochrome waveform — the sound of the product. No photography, no illustration, no gradients.

Scales with font-size · inherits currentColor · animates only while audio plays
Emotion control
Emotion control
feature-emotion.svg
↓ SVG
Multilingual synthesis
Multilingual synthesis
feature-multilingual.svg
↓ SVG
Zero-shot voice cloning
Zero-shot voice cloning
feature-zero-shot.svg
↓ SVG

Feature illustrations stay hairline-weight and monochrome. Don't thicken strokes, fill shapes, or add color.

05 — LAYOUT

One grid, one rhythm

Every Speechify page is built from the same full-width bands on the same grid. The rules are few and strict — follow them and a new page sits flush next to /models and /pricing.

01
One grid, one left edge

An 80rem (max-w-7xl) container with 1.5rem gutters outside the cap, at every breakpoint. Header, footer, and every section share it, so all headings sit on one left vertical. Centering is reserved for a single deliberate block — usually the closing CTA.

02
One vertical rhythm

Every full-width band pads py-section-mobile (4rem) below 768px and py-section (7rem) above. Never a local padding override — one page on a tighter rhythm is the single most visible way a page reads as off-system. A tighter band is a card inside a normal section.

03
Bands strictly alternate

Section backgrounds alternate white and muted (#F5F5F5) down the page. Because sections are optional, muteness is derived from a section's index in the rendered order — never hard-coded — so omitting one can't leave two grey slabs adjacent. The dark closing CTA stays out of the rotation.

04
md is the primary breakpoint

768px is where the system steps: section padding, the heading scale, and the main grid columns all change at md. sm (640px) only reflows dense grids and lg (1024px) only handles two-column hero splits — neither restructures the page. Reach past md sparingly.

hero
proof — index 1, muted
steps — an optional section was omitted above; indices shift, alternation holds
closing CTA — always the ink band, outside the rotation, the only centered block

Inside a section

The internal rhythm is as canonical as the bands. Feature grids use a hairline top rule per item — never a leading bullet dot.

Step Space Rule
Overline → h2 1rem h2: 1.875rem light −0.025em on mobile, 3rem headline at md; max-w-4xl so it never runs past two lines
h2 → intro 1.25rem intro on a max-w-2xl measure; hero subtitle max-w-xl; grid-item body max-w-lg; FAQ max-w-3xl
Header → content 3rem grids, demos, and accordions all start 3rem below the header block; stat rows 2rem below their overline
Content → CTA row 3rem flex flex-wrap items-center; gap-4 between buttons, gap-6 between a button and an ArrowLink
Hero 1.5 / 2.5 / 1.25rem h1 → subtitle → CTA row → reassurance line; fact-pack chips 3.5rem below
Closing CTA 1.25 / 2.5 / 1.5rem ink band, centered max-w-2xl: h2 → copy → buttons → fine print at 60% white

The tokens this page uses

Not a spec in the abstract — these are the exact class strings every band on this page is composed from. Copy them to build a matching surface.

sectionShell
mx-auto w-full max-w-[calc(80rem+3rem)] px-6
The 80rem cap + 1.5rem gutters, encoded on one element. Every band uses it.
eyebrow
font-mono text-[13px] text-muted-foreground
The overline above every h2.
sectionLead
mt-2.5 max-w-[62ch] text-[17px] leading-[1.55]
The intro paragraph measure and rhythm.
py-section
4rem mobile · 7rem ≥ md
The one vertical rhythm token; never overridden locally.
06 — BUTTONS & LINKS

Pills and arrows

Buttons are always fully-rounded pills, always monochrome. One component defines them — src/components/ui/Button.astro — and everything that looks like a button reads from it, so the style can't drift across hand-copied class strings. Weight is Medium; there is no font-semibold in the system.

primary Ink pill — the one true CTA. Repeated, same label, down the page.
secondary Hairline outline. The nudge that must not compete with the key CTA.
ghost Text only. Quiet utility actions.
inverted Near-white on ink — the closing band's primary.
Navigation

ArrowLink is the primary navigation device. Going somewhere is an arrow; doing something is a pill. If every path is a button, none of them reads as the action.

Sizes

lg carries heroes and closing bands; md is the working size inside sections; sm is for dense UI. Hero and closing CTA rows pair one primary with one secondary, never two primaries.

07 — MOTION

Crisp and restrained

Motion confirms, it never decorates. Short ease-out reveals on scroll, and one living element — the waveform — that moves only when sound does.

01
Reveal on scroll, once

Content reveals with data-animate — fade-in, slide-up, slide-in-left/right, scale-in (0.5–0.6s ease-out) or blur-in (0.8s). Stagger siblings with data-animate-delay 1–5 (0.1s steps).

02
The waveform earns its motion

Waveform bars animate only while audio actually plays, then ease back to rest over 280ms. No decorative or looping motion on content.

03
Reduced motion is law

prefers-reduced-motion collapses every animation and transition site-wide, in CSS. Never bypass it, and keep page JS under 10KB.

Vocabulary

data-animate="fade-in | slide-up | slide-in-left | slide-in-right | scale-in | blur-in"
data-animate-delay="1…5" · 0.1s steps · data-animate-children="…" for long containers whose children reveal individually

08 — FAVICONS & ICONMARK

The waveform iconmark

Where the wordmark can't breathe — a browser tab, an app icon, an avatar — the mark collapses to a single glyph: the leading waveform flourish from the wordmark, in a rounded square. It is the one sanctioned icon-only mark, and it is reserved for exactly these square, small contexts. Never use it as a logo in place of the wordmark.

Iconmark on ink
Iconmark on ink

The app-icon form: white glyph on an ink rounded square.

↓ SVG
Iconmark — ink glyph
Iconmark — ink glyph

Transparent, for light surfaces where a container already exists.

↓ SVG
Iconmark — white glyph
Iconmark — white glyph

Transparent, for ink and photographic surfaces.

↓ SVG
Rendered at size
Iconmark at 16px
16px
Iconmark at 32px
32px
Iconmark at 48px
48px
Iconmark at 64px
64px

The glyph is tuned to stay legible down to 16px. Below that, the waveform detail muddies — reach for the ink square with no glyph, or plain text, instead.

The favicon set

Every file below is wired into the site head and derives from the same glyph. Drop the whole set at your web root and reference it exactly as this site does.

SVG (primary) ↓ Download
ICO (16/32/48) ↓ Download
PNG 32 ↓ Download
PNG 16 ↓ Download
Apple touch 180 ↓ Download
PNG 192 ↓ Download
PNG 512 ↓ Download
Web manifest ↓ Download
Head markup

<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png" />
<link rel="icon" href="/favicon.ico" sizes="any" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
<link rel="manifest" href="/site.webmanifest" />

09 — VOICE

How we write

Research-lab confidence, engineering clarity. Lead with capability and numbers, not adjectives.

01
Numbers over adjectives

Lead with latency, languages, and price — <300ms, 30+ languages, $0.07/min — set in mono.

02
Sentence case

Headings and body in sentence case. Short, declarative headlines, often ending in a period.

03
Address the builder

Speak to "you", the developer; the lab is "we". CTAs are imperative: Try the API. Read the docs.

04
No hype

No exclamation marks, no emoji, no superlatives. Honest, side-by-side comparisons are on-brand.

✓ Write this

"Simba 3.2 streams speech with <300ms time-to-first-byte, zero-shot voice cloning, and SSML prosody control."

× Not this

"Our revolutionary, game-changing AI voices will absolutely blow your mind!"

10 — NAMING

Products & models

Product names are proper nouns in sentence case copy. API identifiers stay lowercase and monospaced.

In prose In code Never
Simba 3.2 simba-3.2 "SIMBA", "Simba v3", "the Simba"
Simba 1.6 simba-1.6 "Simba 1.6.0", "old Simba"
Text-to-Speech API client.audio.speech / client.audio.stream "TTS engine", "text to speech tool"
Voice Agents API voice_agents "voicebots", "agent platform"
Developer Platform platform.speechify.ai "dashboard", "console"

The brand is written "SpeechifyAI" — one word, capital S, capital AI — in prose and in the wordmark alike. Never "Speechify AI" with a space, and never "Speechify.ai" as the name. The developer platform is speechify.ai; the consumer app is speechify.com — don't mix them.

11 — ASSETS

Downloads

Every asset on this page, in one place.

LOGO Wordmark — black ↓ Download
LOGO Wordmark — white ↓ Download
ICON Iconmark on ink ↓ Download
ICON Iconmark — ink glyph ↓ Download
ICON Iconmark — white glyph ↓ Download
MOTIF Emotion control ↓ Download
MOTIF Multilingual synthesis ↓ Download
MOTIF Zero-shot voice cloning ↓ Download
ICON Favicon — SVG ↓ Download
ICON Favicon — ICO ↓ Download
ICON Apple touch icon ↓ Download
ICON Web manifest ↓ Download
12 — FOR AI AGENTS

Structured brand specifications

This page is also published as machine-readable plain text. Point your coding agent at speechify.ai/brand/llms.txt (or /brand/llms-full.txt for the full spec) and it will know these rules — logo, color, type, motif, voice, and naming — without a human in the loop.

Questions about usage?

For press inquiries, co-branding, or anything not covered here, write to devrel@speechify.com.

Contact us

Speechify, SpeechifyAI, Simba, and the SpeechifyAI wordmark are trademarks of Speechify Inc. Use of these assets does not imply endorsement, sponsorship, or affiliation. Don't use the marks in your product name, logo, or domain.

Privacy preferences

Choose what we may store on this device. You can change this at any time from the footer.

Strictly necessary

Sign-in, security, load balancing, and remembering your privacy choices. These cannot be switched off.

Always on

Analytics

How the site is used in aggregate - which pages get read, where people get stuck - so we can improve it.

Marketing

Measures which campaigns bring people here, and lets us show relevant ads on other platforms.