Preview title tags across Google, Bing, and browser tabs with pixel-width measurement and truncation alerts.
Search engines do not cut a title when it passes some character count; they cut it where the pixels run out. This tool renders your title the way each surface will show it - Google results, Bing results, a browser tab - measures the rendered width, and flags the point where the ellipsis will appear, with an alert for every view that truncates. The measurement runs in the browser, so a draft title never leaves the page. The common misunderstanding it corrects: 'keep it under 60 characters' is a rule of thumb, not a guarantee, because letter widths vary.
A concrete input and expected output from the current implementation.
Input
Acme Coffee Roasters | Premium Single-Origin Beans Delivered Fresh, Roasted Weekly Since 2012
Expected output
All three previews cut the title with '...' and show a 'Truncated' alert: Google stops at its display boundary, Bing at its own, and the tab at the first phrase. The intact 93-character input is listed below so the cut text can still be read.
At 93 characters the title outruns every surface the tool models: Google's title area (commonly cited at about 600px, roughly 50-60 characters) and Bing's comparable area both cut it, and a browser tab shortens at even fewer characters, so all three alerts fire.
Each preview renders the title with typography approximating the surface's results, measures the rendered width in pixels, and compares it to the surface's display limit. Width decides the cut, so letter shape matters: a title of wide letters like 'W' and 'M' reaches the limit sooner than one of narrow letters like 'i' and 'l'.
Each surface gets its own verdict because the limits differ: Google's title area is the widest, Bing's comparable, and a crowded browser tab can shorten a title to a few words. Alerts appear only for the views that truncate, marking where the ellipsis lands. The simulation stops at measurement: title rewrites, appended site names, and locale-specific fonts are engine behavior the preview cannot predict.
No, and that is the point of measuring by width. Google states no character limit; its English results show a title area commonly cited at about 600px, which usually holds 50-60 characters depending on which letters are used. Bing is similar. The tool reports width against those figures, so treat its verdict as an estimate: engines can still rewrite the title or append your site name.
The most common causes are a title rewrite and the appended site name. Google may replace your title with text it considers more relevant, and it adds the site name to many results, eating width the preview does not model. Font and locale differences can also move the cut a few characters. Keep the essential words at the front - what survives truncation is the beginning.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.