Edition of Tuesday 10 November 2026

Chrome 153 has a native MP4 tab recorder

Comments on “Chrome 153 has a native MP4 tab recorder”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Paul Irish's chrome-capture package uses Chrome's new Page.startScreenRecording DevTools method, which encodes AV1 into an mp4 inside the browser, with optional tab audio and no ffmpeg. That replaces the JPEG-over-CDP route behind Playwright and Puppeteer video. On one M4 Max replay, stop time fell from 3.8s to 17ms and WebSocket traffic from 10.5 MB to 450 KB. The figures are the author's own and unverified, from one workload; 120fps needs a 120Hz display and headful Chrome, and Windows is untested.

Read the original at github.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 16 of 95 with a score of 0.66. The panel rated it highest on new information (0.93) and technical depth (0.89), lowest on audience breadth (0.54). Placed No. 16, No. 22 by score alone: the fourth Programming & dev tools story of the day (−0.020). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Practical, technically detailed write-up of a new Chrome native screen-recording API with benchmarks and a tool release; substantiated with measurements, though a modest audience and some self-promotional framing.
AI judgeJudge 3gpt-5.6-luna
A technically detailed, benchmarked account of Chrome’s new native AV1 tab-recording API, with practical integrations, performance data, and platform caveats. It is highly actionable for browser automation and testing, though narrower than a field-wide development.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.66total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.54
  • Reader interest0.78
  • Audience breadth0.54
  • Practical relevance0.81
  • Substantiated0.83
  • Technical depth0.89
  • New information0.93
  • Counts against: Promotional0.10
  • Counts against: Overclaim0.33

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.600.350.680.540.33+0.24+0.131
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.730.700.900.780.20+0.26+0.202
Audience breadthHow many people who build technology does it concern?0.510.500.620.540.12+0.13+0.071
Practical relevanceHow useful is it to someone who builds software or tech products?0.950.650.820.810.30+0.22+0.177
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.890.700.900.830.20+0.05+0.042
Technical depthHow technically substantive is it?1.000.800.880.890.20+0.05+0.045
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.900.980.930.08+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.080.150.080.100.07−0.19−0.020
OverclaimDo the headline or conclusions claim more than the body supports?0.500.300.200.330.30−0.11−0.037
Sum of contributions+0.657
Claim-check penalty0.000
Total, as published0.657

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #16 on Rubric, 10 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-10/16/"><img src="https://rubric.hrih.si/badge/2026-11-10/16.svg" alt="Ranked #16 on Rubric, 10 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 2 no source given · 6 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkFirst, only or fastest

    Page.startScreencast was the only way to get video frames out of CDP for roughly the past decade.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “For the past ~decade, Page.startScreencast was the only way to get video frames out of CDP”

    The source says

    No passage could be compared.

    Source cited by the article: chromedevtools.github.io/devtools-protocol/tot/Page

  2. Couldn’t checkDate

    The new Page.startScreenRecording CDP method landed in Chrome in September 2026, contributed by Alex Rudenko.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In Sept 2026… the new Page.startScreenRecording landed (thx alex rudenko”

    The source says

    No passage could be compared.

    Source cited by the article: chromium-review.googlesource.com/c/chromium/src/+/7736461

  3. Couldn’t checkCausal conclusion

    With Page.startScreenRecording, frames go from the compositor to an out-of-process encoder over shared memory, and Chrome writes AV1 into the mp4 as it goes.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Frames go straight from the compositor to an out-of-process encoder over shared memory, and Chrome writes AV1 into the mp4 as it goes”

    The source says

    No passage could be compared.

    Source cited by the article: chromium-review.googlesource.com/c/chromium/src/+/7736461

  4. No source givenVersion

    Puppeteer v25.10+ wraps Page.startScreenRecording in an experimental page.record(), deprecating page.screencast().

    The article gives no link or citation for it.

    The article says

    “Puppeteer v25.10+ wraps this in an experimental page.record() (deprecating page.screencast”

    The source says

    No source to compare with.

  5. Couldn’t checkBenchmark result

    In a benchmark of a 6.4s UI replay at 1280x800 on an M4 Max, stop and finalize took 17ms with chrome-capture versus 3,800ms with Playwright recordVideo.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Stop + finalize 3,800ms 17ms”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/paulirish/chrome-capture/blob/main/benchmarks/README.md

  6. Couldn’t checkBenchmark result

    In the same benchmark, WebSocket traffic was 10.5 MB for recordVideo versus 450 KB for chrome-capture, and final file size was 480 KB versus 330 KB.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “WebSocket traffic 10.5 MB 450 KB”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/paulirish/chrome-capture/blob/main/benchmarks/README.md

  7. No source givenNumber

    Chrome's AV1 encoder scales target bitrate linearly with pixel rate, from 2 Mbps at 720p30 to 72 Mbps at 2160p120.

    The article gives no link or citation for it.

    The article says

    “scales target bitrate linearly with pixel rate (2 Mbps at 720p30 -> 9 Mbps at 1080p60 -> 18 Mbps at 1080p120 -> 72 Mbps at 2160p120”

    The source says

    No source to compare with.

  8. Couldn’t checkBenchmark result

    On a 120Hz ProMotion Mac in headful mode, chrome-capture achieved 1080p and 2160p at 120fps (119.9 fps, 59.8 Mbps).

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Mac (--headful on 120Hz ProMotion): 1080p @ 120fps and 2160p @ 120fps 😲 (119.9 fps, 59.8 Mbps AV1 + stereo Opus”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/paulirish/chrome-capture/blob/main/examples/capture-demos.ts

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 3 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Chrome 153 has a native MP4 tab recorder”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.67

    Semver Trick