Editorial Policy

Who writes this blog

Articles are published under the byline "RenderComp Team". RenderComp is a catalog of Remotion templates built and maintained by the RenderComp team, and the blog is run by the same team that builds the templates. Topics come from the Remotion behavior we deal with while designing, rendering, and maintaining those templates.

We do not attach individual author names. Questions about an article go to the team through the contact below.

Why we publish it

The blog is for developers who build video programmatically with Remotion (React + TypeScript). It records API behavior, edge cases, and parameter trade-offs that are hard to get from skimming the official docs, always alongside runnable code. It is written as technical writing, not advertising: an article mentions the RenderComp catalog at most once.

How we use generative AI

Articles on this blog are drafted with generative AI (a large language model). This is the extent of that use:

• Topic and scope: the subject, the APIs covered, and the tags are chosen from a topic list prepared by the team.
• Drafting: given the topic and our writing rules (use only real Remotion APIs, invent no anecdotes or statistics, state no prices, reference no external CDNs, and so on), the model writes the English and Japanese versions separately. The Japanese article is a counterpart written from the same brief, not a word-for-word translation.
• The animation at the top of an article: it is rendered from an actual template in the catalog, from its React component. The composition ID, props, resolution, and fps used for the render are recorded in the article's metadata.

Before publication every article goes through automated checks. An article that fails any of them is not published:

• statistics, percentages, or counts stated without a source
• unfounded first-hand claims such as "we tested this" or "a customer told us"
• any price mentioned must match the published pricing (as listed in llms.txt)
• internal links must point to pages that exist; external URLs must respond
• no external CDNs (such as Google Fonts), external scripts, or iframes
• no in-house jargon that readers outside the team would not use
• (Japanese articles) no deviation from the house style profile

These checks stop specific kinds of errors mechanically; they do not guarantee that everything in an article is correct. If you find a mistake that got through, please tell us using the contact below.

Numbers, prices, and claims

• Prices: we use only the prices on our published pricing page. Article bodies do not state RenderComp prices as a rule; the pricing page is the reference.
• Template count: we use only the catalog's published figure (1,000+).
• Numbers in code: frame counts, fps, spring stiffness, interpolation ranges, and similar values are the parameters used in that article's examples. They are not benchmarks.
• Statistics and studies: we do not publish statistics we cannot source, nor invented benchmarks, quotes, or surveys. When an article relies on outside statistics or documents, they are listed under "Sources" at the end of the article.
• Sponsored posts and affiliates: we do not accept sponsored articles and do not use affiliate links.

Reporting an error

If you find an error, an outdated statement, or code that does not run, contact us through the support page or at [email protected]. Including the article URL and the passage in question helps. We verify the report, fix the article, and show an updated date on corrected articles.

Updates

Each article reflects the Remotion API as of its publication date. When a Remotion release makes an article outdated, we revise it, or retire it if it cannot be revised. Revised articles show an updated date alongside the original publication date.

Operator

RenderComp and this blog are operated by the RenderComp team. Company details are in the Legal Notice; how we handle personal data is in the Privacy Policy.