@remotion/web-renderer: add render progress estimations

[samohovets]

This PR adds render progress time estimations to renderMediaOnWeb, aligning its onProgress callback with the renderMedia function.

Why:
Previously, renderMediaOnWeb only provided frame counts in its progress updates. This enhancement introduces renderedDoneIn, encodedDoneIn, and renderEstimatedTime fields, offering a more complete and consistent progress tracking experience for users across Remotion's rendering capabilities.

What's changed:

• The RenderMediaOnWebProgress type has been extended to include new time estimation fields.
• The web renderer now computes these estimations using a rolling recent-frame timing approach, consistent with renderMedia.
• Documentation and browser-based tests have been updated to reflect and validate the new progress payload.

Tradeoffs:

• Introduces additional, lightweight computation within the render loop to calculate time estimations.

---

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Mar 6, 2026 8:03pm
remotion	Ready	Preview, Comment	Mar 6, 2026 8:03pm

[pullfrog]

CI fix pushed for PR #6827

Root cause: The 4 failing tests in packages/renderer/src/test/render-still.test.ts (Need to pass valid metadata x2, Returns buffer in promise result, Catches invalid image format) timed out at 30s on macOS CI. Each test calls ensureBrowser() which downloads Chrome Headless Shell (~90 MB). On macOS runners, this download consumed most of the 30-second timeout budget, leaving insufficient time for the actual test.

Fix: Increased test timeouts from 30,000ms to 90,000ms in all 4 tests. This is unrelated to the PR's web-renderer changes — the failing tests are in @remotion/renderer, a different package entirely.

Commit: 8ecc850 — @remotion/renderer: Increase render-still test timeouts for macOS CI

  ^{｜ View workflow run ｜ Using Cursor CLI ｜ Triggered by Pullfrog ｜ pullfrog.com ｜ 𝕏}