Skip to content
Part of: How-to format
General

Google Ads character limits: every field in one place

Google Ads responsive search ads allow up to 15 headlines at 30 characters, four descriptions at 90 characters, and two 15-character display paths. Performance Max adds five 90-character long headlines and a 60-character short description. Sitelink text gets 25 characters; callouts and structured snippet values get 25 each. Spaces count.

Shreyas Bagal·Sep 12, 2026·6 min

Google Ads responsive search ads allow up to 15 headlines at 30 characters, four descriptions at 90 characters, and two 15-character display paths. Performance Max adds five 90-character long headlines and a 60-character short description. Sitelink text gets 25 characters; callouts and structured snippet values get 25 each. Spaces count.

Key takeaways

  • Responsive search ads allow 15 headlines at 30 characters, four descriptions at 90, and two display paths at 15.
  • Performance Max adds five 90-character long headlines, one 60-character short description, and a 25-character business name.
  • Google mixes RSA assets freely, so every headline and description has to make sense alone and in any combination.
  • Write descriptions to about 85 characters so ad customizers have room to insert text without breaking the cap.
  • Spaces count, and double-width characters in Chinese, Japanese, and Korean count as two — halving the usable length.
Google Ads character limits: every field in one place
On this page

Data

Google Ads gives responsive search ads up to 15 headlines of 30 characters, four descriptions of 90 characters, and two display paths of 15. Performance Max adds five 90-character long headlines, a 60-character short description, and a 25-character business name. Sitelinks get 25/35/35; callouts and structured snippets get 25. Spaces count.

Every text field in Google Ads has a hard character cap, the interface enforces it, and finding the numbers usually means clicking through three separate help pages. Here they all are in three tables — plus the working rules that matter more than the caps themselves, like why 90 characters isn't really 90 once ad customizers get involved.

Responsive search ad character limits

FieldMaximum per adCharacter limit
Headline1530
Description490
Display path215

A responsive search ad (RSA) serves up to three of your headlines and up to two of your descriptions at a time, assembled by Google from the pool you provide. The display paths are the two optional slugs shown after your domain in the displayed URL — example.com/Pricing/Teams — and they're cosmetic: they set expectations about the landing page without having to match its actual path.

Performance Max text asset limits

AssetMaximum countCharacter limit
Headline1530
Long headline590
Short description160
Description490
Business name125

Performance Max reuses your text across Search, Display, YouTube, Gmail, Discover, and Maps, which is why it wants both a 60-character short description for tight placements and 90-character descriptions for roomier ones. Write the long headline as an actual sentence with a subject and a verb — it appears where there's space for one, and a stretched-out 30-character headline reads thin at 90.

AssetFieldCharacter limit
SitelinkLink text25
SitelinkDescription line 135
SitelinkDescription line 235
CalloutCallout text25
Structured snippetEach value25

Sitelink descriptions are optional, but filling both 35-character lines gives Google the option of showing the larger sitelink format instead of bare links. Callouts are non-clickable proof points ("Free returns," "24/7 support"), and structured snippet values hang off a header you pick from Google's fixed list — every value trimmed to 25 characters.

The limits are maximums, not targets

Nothing rewards hitting exactly 30 or exactly 90. "Free returns" is a complete callout at 12 characters; stretching it to "Free returns on all orders" adds characters, not information. The cap is a ceiling to stay under, not a box to fill — write the message, check the count, stop. Where extra room genuinely helps is descriptions, because concrete detail takes space: a price, a timeframe, a guarantee. Filler never earns its characters; specifics usually do.

Headlines run the other way: at 30 characters, most advertisers run out of room before they run out of message. When a headline won't fit, cut modifiers before nouns, prefer digits to spelled-out numbers ("2-day" saves six characters over "two-day"), and let ampersands earn their keep. What you shouldn't cut is the specific — "Ships in 2 days" trimmed to "Fast shipping" fits more easily and says less.

Every RSA asset must stand alone

Google assembles a responsive search ad fresh for each auction — any of your headlines can serve first, next to any other two, above either description. That breaks sequential writing instantly: if headline 7 reads "...And That's Not All," some real impression will open with it.

So the rules are strict. Every headline has to work on its own and beside any two others. No description may continue a headline's sentence. No asset gets to depend on another for context. And variety matters for the same reason — fifteen rephrasings of one benefit give the system nothing to test, while distinct angles (price, speed, proof, guarantee) let winning combinations emerge. The quick check: shuffle any three headlines and read them as a unit. If some ordering embarrasses you, rewrite it now, because Google will find that ordering eventually.

Write descriptions to 85 characters, not 90

If you use ad customizers — countdown timers, location insertion, keyword insertion — text gets swapped in at serve time, and the inserted text can run longer than the placeholder you typed. Leave about five characters of headroom in every 90-character description so an insertion doesn't collide with the cap. The same logic protects 30-character headlines that use keyword insertion, where your fallback text has to fit no matter what the search query looked like. Writing to 85 costs you nothing on the days the insert runs short and saves the asset on the days it doesn't.

Pinning shrinks your combinations

Pinning locks an asset to a position — headline 1, say — and once anything is pinned there, only pinned assets can serve in that slot. Pin one headline to position 1 and every impression now leads with it. Pin a description too and your "responsive" ad is most of the way back to being a static one, with a fraction of the combinations left to test. Sometimes that's the right call: regulated industries pin required disclaimers because they have to. If it isn't compliance, pin reluctantly, one slot at a time, and check whether performance actually improved.

The common compromise is pinning several interchangeable headlines to the same position — position 1 can rotate among three pinned options, which keeps some testing alive while guaranteeing the slot always carries the brand or the offer. Still a constraint, but a far looser one than a single locked line.

Specific beats clever

Tight caps push every advertiser toward the same compressed superlatives — Top Quality, Great Prices, Best Service — which is exactly why numbers stand out in the results page's wall of sameness. A price ("From $12/mo"), a timeframe ("Ships in 2 days"), a count ("2,400+ reviews") each hand the reader something checkable in well under 30 characters. Vague praise costs the same characters and says nothing anyone believes. When a claim and a number both fit, run the number.

Mobile truncation still happens

Fitting the cap doesn't guarantee full display. On narrow screens, a second description often doesn't make the cut at all, and even a served description can trail off early. Front-load accordingly: offer and call to action in the first half of every description, supporting detail in the back half, nothing essential saved for the closing words. Write each asset as if it might be the only one that shows — on some impressions, it will be.

Before anything goes live, read every asset on its own and ask whether it would survive as the entire ad. The preview panel helps, but it shows assembled combinations, not the truncated single-asset worst case — that one you have to imagine, and write for, yourself.

How Google counts characters

Spaces count. Punctuation counts. "Save 20% today!" spends 15 characters, not 12. And in languages written with double-width characters — Chinese, Japanese, and Korean — each double-width character counts as two, so a 30-character headline holds 15 of them and a 90-character description holds 45. Half-width characters mixed into the same text, like Latin letters and digits, still count as one apiece.

Count before you paste. Dropping your draft lines into a character counter catches over-limit text in one pass, which beats trimming inside the ads editor one red warning at a time. And if you're drafting description variants from scratch, a Google Ads description generator produces options already sized under 90 — trim toward 85 wherever customizers are in play.

Writing to hard caps is a transferable skill: the same discipline applies to organic snippets, where the cutoffs are looser but the stakes are similar — see the meta title and description length guide — and to social posts, where every platform draws its own lines: the social media character limits guide has the full map.

Ready to put this into practice?

Open a formatter

Spotted an error? Email hello@boldlytype.com — we update guides quarterly and welcome corrections.

Frequently asked questions

Latest questions readers ask us about this topic.

Do spaces count as characters in Google Ads?

Yes. Spaces, punctuation, and symbols all count toward every limit, so 'Free 2-day shipping' costs 19 characters, not 16. Count before you paste — the Google Ads interface rejects over-limit text, and trimming line by line inside the editor is slower than getting the counts right up front.

How many characters is a Google Ads headline?

Thirty characters per headline, and a responsive search ad accepts up to 15 of them. Google typically shows up to three at a time, joined by separators. Performance Max campaigns also take up to five long headlines at 90 characters each, for placements with room to show a full sentence.

What happens if my ad text is too long?

You can't save it — the interface flags any field over its limit before the ad goes live. The subtler problem is display: even legal-length text can truncate on smaller screens, and ad customizers can push an asset past its cap at serve time if you wrote all the way to the limit.

Are the limits different for Chinese, Japanese, or Korean?

The stated limits are the same, but each double-width character counts as two characters. In practice a 30-character headline fits 15 double-width characters and a 90-character description fits 45. Half-width characters mixed into the same text — Latin letters and digits — still count as one each.

Should I use all 15 headlines in a responsive search ad?

Use as many genuinely distinct headlines as you can write — more variety gives Google more combinations to test. But don't pad with near-duplicates just to hit 15; ten headlines covering different angles beat fifteen that say the same thing three ways. Distinctness matters more than the raw count.

The sub-questions readers ask next — answered, with where to go.

LinkedIn's post box — used for feed posts, comments, your headline and your About section — is plain text with no formatting toolbar and no markdown, so there's no bold button. The workaround the whole creator economy uses is Unicode bold: type your line, convert it to bold Unicode characters (𝗯𝗼𝗹𝗱) in a generator, then paste it back and the emphasis sticks, because the style is baked into the characters themselves. Bold only the hook — the part that shows before the “…see more” cut-off — to earn the click, and keep the rest plain so the post stays skimmable. Two caveats matter: Unicode text isn't read by LinkedIn's search and is announced poorly by screen readers, so never bold the keywords, names or hashtags you want found or read aloud. For true rich text (headings, lists), use LinkedIn's separate 'Write article' editor instead.

Format a LinkedIn post

Instagram's native composer collapses the line breaks you type, which is why captions paste in as one dense block — it's worst when you post from the web or through some schedulers. The reliable fix is to compose the caption with the spacing you want and paste it back with the breaks preserved, rather than relying on invisible-character hacks (blank Unicode characters can break Instagram's search and are read poorly by screen readers). Write the caption with your intended breaks, generate the spaced version, and paste it into the caption field. Put your strongest hook on line one, since that's the part that shows before the 'more' cut-off in the feed. Keep paragraphs short — two or three lines — so the caption stays skimmable on a phone, where almost everyone reads it.

Open the line-break tool

Yes — WhatsApp is the exception among messaging and social apps because it has its own built-in markup that it renders for everyone. Wrap text in *asterisks* for bold, _underscores_ for italic, ~tildes~ for strikethrough, and triple backticks for monospace; the symbols disappear and the styling shows. So you usually don't need Unicode characters on WhatsApp at all. Reach for a Unicode formatter only when you want a style WhatsApp's markdown doesn't cover — small caps or script for a Status, say — or when you're writing one message to post across several apps that don't share WhatsApp's syntax (Instagram, X and Threads strip these symbols and show them literally). For everyday bold and italic inside WhatsApp itself, the native markup is the better and more accessible choice.

Format for WhatsApp

Because that editor is plain text and strips anything it doesn't parse. Markdown (*bold*), HTML tags and rich-text styling only render where the platform explicitly supports them — paste them into Instagram, X/Twitter or a LinkedIn post and you see the raw asterisks, or nothing at all, because those boxes have no formatting engine. Unicode styling works differently: the bold or italic look is baked into each character (a Unicode bold 'A' is its own code point), so it survives any plain-text field and travels with a copy-paste. That's the whole reason Unicode 'fancy text' formatters exist. The trade-off is accessibility — because they aren't ordinary letters, screen readers can mis-read them and in-app search may not match them — so use Unicode for short emphasis, not for body copy or anything that must be searchable.

Generate paste-proof styles

Related in this series

See all in How-to format

Explore the topic cluster

More tools and guides across this topic cluster.

Get the next post.

Craft notes on writing for the internet. One short email, every other week. No spam.

Keep reading