Chrome for Developers engagement report
@ChromiumDev - 423K followers on X
Measured over 26 original posts from a 30-day window, last computed on August 30, 2026.
Engagement
A typical post picks up 128 interactions against 423K followers, an engagement rate of 0.03%. Measured over 26 original posts, its engagement rate beats 47% of 3,739 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 15K times each, and 0.84% of those impressions turn into an interaction. That is about 3.60% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.3 post a day over the last 30 days, with activity on roughly 70% of days. Most posts go out around 19:00 UTC, and Friday is the busiest day of the week. Of the 26 posts sampled, 85% carry an image or video and 92% link out. The account's strongest tracked post pulled 8.6K interactions, about 67x its own typical post.
Measured over 26 original posts from a 30-day window, last computed on August 30, 2026.
Compared with accounts its own size
Chrome for Developers's engagement rate beats 47% of the tracked X accounts closest to it in follower count (3,739 accounts, accounts of similar size (decile 7 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.
On engagement per impression rather than per follower it beats 46% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.
Where this sits in the catalog
At 0.03%, Chrome for Developers sits above the 25th percentile of the 36,134 accounts in this comparison. That places it in the below the median band, which runs 0.012% to 0.08%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.002% |
| 25th percentile | 0.012% |
| 50th percentile | 0.08% |
| 75th percentile | 0.431% |
| 90th percentile | 2.11% |
| 99th percentile | 161.6% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 19:00 UTC, and Friday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 50K |
| 01:00 UTC | -2% | 51K |
| 02:00 UTC | -4% | 49K |
| 03:00 UTC | -4% | 53K |
| 04:00 UTC | -6% | 42K |
| 05:00 UTC | -4% | 41K |
| 06:00 UTC | -4% | 47K |
| 07:00 UTC | -5% | 51K |
| 08:00 UTC | -4% | 60K |
| 09:00 UTC | -3% | 68K |
| 10:00 UTC | -2% | 71K |
| 11:00 UTC | -3% | 77K |
| 12:00 UTC | -2% | 85K |
| 13:00 UTC | -2% | 93K |
| 14:00 UTC | -3% | 96K |
| 15:00 UTC | -2% | 99K |
| 16:00 UTC | -3% | 96K |
| 17:00 UTC | -2% | 89K |
| 18:00 UTC | -2% | 83K |
| 19:00 UTC | -2% | 79K |
| 20:00 UTC | -1% | 73K |
| 21:00 UTC | -1% | 65K |
| 22:00 UTC | -1% | 57K |
| 23:00 UTC | -2% | 51K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +4% | 228K |
| Monday | 0% | 281K |
| Tuesday | -2% | 270K |
| Wednesday | -1% | 249K |
| Thursday | -2% | 242K |
| Friday | -3% | 250K |
| Saturday | +3% | 225K |
Best tweets
- Jul 23, 202667x their median
Introducing Canvas UI, the first ever html-in-canvas component library. Your DOM is the render target now. Real-time shaders over real, interactive UI. 24 components. React, Vue, Svelte, vanilla TS. Free. Open source. 🧵 https://t.co/Y5ZZDNxPUX https://t.co/zrHgmlH1Mg
- Aug 25, 202632x their median
The WebMCP Challenge is here. We’ve teamed up with @ChromiumDev, @CloudflareDev, @ShopifyDevs, @vercel, @render, and @Netlify for a 10-day hackathon. Up for grabs: $35,000 in cash prizes, Codex Micros, ChatGPT Pro subscriptions, and more prizes from our supporters. https://t.co/J7CGKSxggZ
- May 16, 202513x their median
Introducing 🤯 flex-wrap: balance 🤯 Would you use this? ⚠️ Not a "real" feature yet, just something one of our engineers has been working on. (You can try it out in the latest Chrome Canary with the experimental web platform features flag though!)
- Jul 29, 20265.7x their median
What if we could remove the friction in the email → https://t.co/Xn4t0XWCMP The proposed Email Verification API would let your site validate the email address right in the browser! No email sent, no confirmation click needed. https://t.co/1r5bQuxxqE
- Aug 10, 20262.9x their median
Use the built-in Prompt API with the Vercel AI SDK to build AI-powered web applications with client-side models → https://t.co/w4M7q3z5sy https://t.co/KfajNDxx0w
- Aug 6, 20262.3x their median
Web apps just got a major speed boost for pasting. Until now, https://t.co/SURKba7MDn() fetched and sanitized every data format on your clipboard upfront, wasting CPU and memory on data your app didn't even need. Starting in Chrome & Edge 149, the Async Clipboard API switches to Selective format read. What changes? ClipboardItem now acts as a lazy handle. Bytes are only read and sanitized when you call getType(). The payoff? Instant latency drops, massive memory savings, and zero code changes required. Catch all the details and one important behavior change to watch out for → https://t.co/baiIPYaeTl
- Aug 21, 20262.0x their median
Skip writing complex JavaScript to make form elements like textarea fit user input 🍝 The field-sizing CSS property is a newly available Baseline feature that lets form controls naturally adjust their sizing to fit their contents. Find the documentation here → https://t.co/yaNlmlCJWY
- Aug 26, 20261.8x their median
Chrome 152 is here with new tools to enhance your web apps. Discover new CSS pseudo-elements, the CPU Performance API, and Connection Allowlists in the latest release ⬇️ https://t.co/DP2C7q42rK
- Aug 6, 20261.8x their median
Your coding agent can now make your website better for visiting AI agents. Lighthouse audits are now available inside DevTools for agents, including the new agentic browsing category. See how to build a closed feedback loop for this and 4 other categories of web fixes → https://t.co/fzTwdLv3gY
- Aug 12, 20261.5x their median
Meet Chrome DevTools Connect for WebStorm → https://t.co/2NqocqFABf Now your AI agent can open Chrome, inspect rendering, read console logs, and verify runtime fixes without you leaving the WebStorm IDE. https://t.co/YWKDnTZfjx
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Buy or sell X accounts - escrow-protected
PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 128 interactions against 423K followers, an engagement rate of 0.03%. Measured over 26 original posts, its engagement rate beats 47% of 3,739 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 15K times each, and 0.84% of those impressions turn into an interaction. That is about 3.60% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.3 post a day over the last 30 days, with activity on roughly 70% of days. Most posts go out around 19:00 UTC, and Friday is the busiest day of the week. Of the 26 posts sampled, 85% carry an image or video and 92% link out. The account's strongest tracked post pulled 8.6K interactions, about 67x its own typical post.
- What is Chrome for Developers's engagement rate on X?
- Chrome for Developers (@ChromiumDev) has an engagement rate of 0.03%, based on the median interactions across 26 original posts from the last 30 days against 422,992 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.03%, Chrome for Developers sits above the 25th percentile of the 36,134 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @ChromiumDev have real engagement?
- Its engagement rate beats 47% of the tracked X accounts closest to it in follower count (3,739 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
- When does @ChromiumDev post?
- Most posts go out around 19:00 UTC, and Friday is its busiest day, at roughly 1.27 posts per day across the measured window.