Skip to content

docs: add Hyperframes vs Remotion comparison to README#329

Closed
Muyideen-js wants to merge 1 commit intoheygen-com:mainfrom
Muyideen-js:docs/readme-hyperframes-vs-remotion
Closed

docs: add Hyperframes vs Remotion comparison to README#329
Muyideen-js wants to merge 1 commit intoheygen-com:mainfrom
Muyideen-js:docs/readme-hyperframes-vs-remotion

Conversation

@Muyideen-js
Copy link
Copy Markdown

Closes #318

Summary

Adds a short Hyperframes vs Remotion section to the README with a pros/cons-style table so people can tell which authoring model and stack fits them.

Motivation

Some areas of the project share implementation patterns with tools like Remotion (browser capture, FFmpeg, etc.). Documenting the product-level differences (HTML-first vs React-first, ecosystem tradeoffs) makes it easier to choose the right tool.

What changed

  • New section after Why Hyperframes? with:
    • Brief context on overlap vs differences
    • Table: authoring model, pros, cons
    • One-line rough guide for when to pick each

Checklist

  • README only (documentation)

@jrusso1020
Copy link
Copy Markdown
Collaborator

Thanks for taking a swing at this, @Muyideen-js 🙏 — genuinely appreciate the effort to get #318 resolved.

We ended up shipping the comparison through #355 (merged) based on an internal write-up by the team, so it could go deeper on the architectural tradeoffs (library-clock animations, HTML passthrough, visual editing, HDR, licensing) and include a GSAP side-by-side. Closing this one as superseded — but please keep contributing, there's lots more in the issue tracker we could use help on.

@jrusso1020
Copy link
Copy Markdown
Collaborator

Superseded by #355.

@jrusso1020 jrusso1020 closed this Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hyperframes vs Remotion

2 participants