/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

remotion-dev/remotion

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:50:45.529Z

1mo ago

remotion-dev/remotion

Remotion is an active, high-popularity monorepo for creating videos programmatically with React. It targets developers building video generation, rendering, and editing tooling, with a large package surface spanning core rendering, player, studio, media handling, templates, and serverless workflows. The repository is very active as of 2026-03-30 and appears maintained for ongoing product and docs changes.

Loading tags...

Stars41,269

Forks2,650

Default branchmain

Last pushed2026-03-30T15:31:20Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream unless you specifically need an older, curated Remotion snapshot. This fork looks stale and materially behind, with only a few early player/docs tweaks and no evidence of ongoing maintenance.

Choose this fork only if you specifically want its local customizations and can absorb the cost of a very large upstream gap. For most adopters, upstream Remotion is the safer choice.

Choose this fork only if you need its older baseline or custom repo workflows; for most adopters, upstream Remotion is the better choice because this fork is materially stale and likely missing major recent fixes and features.

Prefer the upstream Remotion repo unless you specifically need this older snapshot. This fork has no visible fork-only features and is materially behind upstream, so it is a poor adoption choice for users who want current capabilities or fixes.

Prefer this fork only if its custom workflow is the product and you can absorb long-term maintenance. For general Remotion adoption, upstream is the safer choice because this fork is heavily behind and materially diverged.

Prefer this fork only if its custom behaviors are specifically required and you are willing to own a substantial maintenance backlog. For most adopters, upstream Remotion is the better starting point because this fork is materially stale and highly divergent.

Choose this fork only if you need its legacy behavior or local customizations and do not plan to track upstream closely. For most adopters, upstream Remotion is the better default because this fork is materially outdated and costly to maintain.

Prefer upstream unless you specifically need this fork's older snapshot or its small custom content changes. For most adopters, the maintenance gap and extreme divergence make it a poor default choice.

Choose this fork only if you specifically need its old rendering/runtime experiments or legacy behavior. For most users, upstream Remotion is the better choice because this fork is extremely stale, heavily diverged, and likely missing many years of fixes and features.

Choose the upstream project unless you specifically need this frozen 2021 fork or its local workflow customizations. For most adopters, the fork is too stale and too far behind to be a practical base.

Fork comparison

codediodeio/remotion

38/100

stale

significant_divergence

Prefer upstream unless you specifically need an older, curated Remotion snapshot. This fork looks stale and materially behind, with only a few early player/docs tweaks and no evidence of ongoing maintenance.

Likely purpose

An older, lightly customized Remotion snapshot likely kept for experimentation, tutorials, or a frozen reference rather than as a current production base.

Best for

Developers who want an archived or educational snapshot of Remotion rather than the latest framework.; Teams studying older player behavior or early documentation examples.; Users who prefer a frozen fork they can modify in isolation and do not need to stay current with upstream.

Additional features

Older player and media-handling refinements from 2022, including player improvements and fixes for non-seekable media and scaling behavior.
Documentation-oriented changes around `useCurrentFrame`, stills, and sequence usage that suggest the fork was tuned for learning or examples.
A frozen codebase that may be easier to study or patch for a narrow workflow because it avoids the churn of the much larger upstream monorepo.
Extends or customizes major product areas around `.claude/commands/` and `.claude/skills/add-cli-option/`.

Missing features

It is far behind upstream and likely misses years of Remotion releases, fixes, and package additions after March 2022.
Recent upstream work in Studio, media handling, Google Fonts, lambda/serverless, and docs is absent here.
Many newer workflows and APIs from the active upstream monorepo are unlikely to be available or reliable in this fork.
The fork appears to lag on maintenance and would be harder to use as a drop-in base for current Remotion projects.
It trails upstream by 2265 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Small community fork with a focused, older codebase.
May be suitable for reproducing or preserving behavior from the early-2022 Remotion era.
Could be useful if you specifically want the fork owner's documentation or player tweaks rather than current upstream behavior.

Risks

Very stale relative to upstream, with a large behind count and no recent pushes.
High migration cost if you need current Remotion APIs, fixes, or package layout.
Potentially missing security, compatibility, and rendering fixes accumulated upstream since 2022.
The large diff suggests substantial divergence, so upstream documentation or support may no longer match this fork.