Nexrender review: what it does well, where it stops

Search for a nexrender review and most of what ranks is written by rival vendors. Plainly maintains a dedicated nexrender alternative page and its own review of the project, and nexrender's blog answers in kind with a Plainly alternatives post. None of that is scandalous, it is simply how search economics work, but it does mean the "reviews" are mostly sales collateral wearing a review's clothes, and the takedown style some of them adopt tells you more about the author than the software.

This is a vendor piece too, so the bias goes on the table in the first paragraph: we build Nubu, a creative automation platform whose render farm drives real After Effects at production scale. That is also our claim to be worth reading on this subject. We automate After Effects for a living, we have built and operated the kind of infrastructure nexrender provides, and we think it is good software with a clear, deliberate boundary. This review describes what nexrender is genuinely good at, what running it actually involves, where it stops on purpose, and then a fair set of alternatives, including the case where the right answer is nexrender itself.

The one-paragraph verdict, for the impatient: nexrender is the reference open source answer to After Effects render automation, and for engineering teams that want free software, total control and the ability to embed rendering inside their own product, it is the right choice. It is an engine, not a workflow: there is no review UI, no approval step and no delivery, so the moment non-developers need to participate, you are either building product around it or buying one.

What nexrender is#

nexrender (github.com/inlife/nexrender) is open source After Effects render automation: free, self-hosted, and developer-oriented, with several thousand GitHub stars. It automates the versioning-and-rendering problem that every scaled After Effects pipeline eventually hits: you have one project, you need many outputs that differ in text, footage and data, and no human should be doing that by hand.

The design is admirably plain. A render job is a JSON document. The document names the After Effects project, the composition to render, and the changes to make before rendering: text values to set, footage to swap. nexrender applies those changes and drives the render through aerender, the command line renderer that ships inside every After Effects install. In other words, it does what a careful technical artist would do manually, except encoded, repeatable and unattended.

Two ways to run it. The CLI suits a single machine: hand it jobs, it renders them. The server-and-workers model is the scaled version: a server holds the queue, worker machines pull jobs from it, and together they form a render farm on hardware you own, with your own After Effects licences on each worker. That is the entire pitch, and for its audience it needs no decoration: your data pipeline emits job documents, your machines turn them into video, and every part of the system is yours to inspect, modify and extend.

Why developers like the job model#

It is worth pausing on why this design has earned its reputation, because the reasons are real.

Jobs are data. A JSON document can be generated by any language, stored in any database, queued in any system and diffed in any code review. Your rendering pipeline becomes ordinary software, testable and versionable like the rest of your stack.

The engine is genuine After Effects. Because rendering goes through aerender against your actual project, whatever your motion designers built is what renders. There is no lookalike renderer imposing a fidelity ceiling, and no list of supported features to check your project against.

It embeds. This is the property none of the SaaS platforms in this article can offer, ours included. If your product needs to generate After Effects quality video for your own users, inside your own software, on your own infrastructure, an open source engine you can wrap, fork and ship is the correct shape, and nexrender is the established one.

It costs nothing to license, forever. No per-seat fees, no metered minutes, no contract. At sustained volume, with engineers already on the payroll, the marginal cost of a render approaches the electricity, and no pricing page competes with that.

What self-hosting really involves#

Now the part the takedown reviews weaponise and the fan posts skip. Neither is necessary: the costs of self-hosting are not hidden, they are simply the deal, and they deserve a sober list. Running nexrender in production means owning, at minimum:

Machines. Rendering After Effects is heavy work, and the workers doing it are real computers you provision, whether physical boxes in the studio or cloud instances. They need enough memory to render your projects, and they need looking after: updates, disk space, the works.

After Effects licences. Each worker drives a licensed After Effects install. The software driving AE is free; After Effects itself is not, and licensing is between you and Adobe.

Environment parity. Every font and every plugin your templates use must exist, at matching versions, on every worker. A missing font does not fail loudly at submission time; it renders wrongly or falls over mid-queue, and keeping a fleet of render machines identical is a genuine operational discipline.

Queue stewardship. Someone owns the farm's health: watching queue depth, deciding what happens when a render fails at 2am, cleaning up stuck work, scaling workers when a campaign lands. None of this is exotic to an engineering team, all of it is time, and the person spending that time is usually your most expensive one.

Everything around the engine. This is the largest line item and the least visible. nexrender takes job documents in and puts rendered files out. A form a marketer could submit from, somewhere to preview and approve outputs, a route from approved file to ad account or client: all of that is software your team designs, builds and maintains. For a product team embedding video, that surrounding software is the product they were building anyway, so the cost dissolves. For a marketing team, it is a second product they did not plan to own.

If you want the whole landscape these trade-offs sit inside, from expressions to desktop plugins to hosted platforms, our After Effects automation guide maps it end to end.

Where nexrender genuinely shines#

Put the costs and the design together and the profile of the right nexrender user is sharp.

Product teams embedding video. If AE-quality video generation needs to live inside your own software, this is the tool. SaaS platforms rent you their pipeline; nexrender lets you build yours, and no subscription product, ours included, can match that.

Teams that need total control. Regulated data that cannot leave your infrastructure, unusual pipeline requirements, a need to inspect and modify every stage: open source you host yourself answers all of it by construction.

Engineering-led studios at volume. With real render volume and engineers who enjoy owning infrastructure, free software on your own machines is the cheapest possible way to render, and the control is a feature rather than a burden.

Anyone allergic to lock-in. Jobs are JSON, projects are your own .aep files, machines are yours. There is nothing to migrate away from because nothing was ever surrendered.

Where it stops, on purpose#

The boundary is as clean as the design. nexrender is developer-oriented: there is no review UI, no approval workflow, and no delivery. Those are not missing features; they are out of scope for a render engine, and the project is disciplined about its scope.

But the boundary is exactly where most teams' problems live. In our experience the render is the middle of the job. Before it comes the versioning logic and the data. After it comes the part that involves other human beings: someone checks the outputs, someone signs them off, someone gets the approved files to the ad account or the client, and someone answers for which version went where. nexrender, correctly, does none of this. The moment a colleague who does not read JSON needs to see, comment on or approve a render, you are building interface, permissions, notifications and audit trail around the engine, and that surrounding software is routinely more code than the rendering ever was.

So the honest test for self-hosted nexrender is not "can our engineers run it" (if you have engineers, yes) but "who besides engineers has to touch the pipeline, and what will we build for them?" If the answer is nobody, nexrender may be all you ever need. If the answer is a marketing team, a client, or an approval chain, keep reading.

Nexrender Cloud: the managed middle#

The project's own commercial arm answers part of this. Nexrender Cloud is the managed offering: the same job model with the machines, licences and scaling handled for you. As listed on their pricing page: Pay-As-You-Go at €99 per month plus €0.18 per render minute, a Dedicated Engine at €350 per month, and custom Enterprise pricing.

That dissolves the self-hosting section of this review, which is a genuine service worth paying for, and it keeps the developer-friendly job model intact. What it does not change is the shape of the tool: rendering as a service for people comfortable driving it programmatically. The review, approval and delivery layers remain yours to provide. If your gap was machines, Nexrender Cloud closes it; if your gap was workflow, it does not.

The alternatives, fairly#

Different gaps, different tools. One disclosure before the table: Nubu is our product, and it keeps its place in this list for the same reason each entry does, because it fits a specific profile best.

Nexrender Cloud#

Covered above, and listed here for completeness because it is the lowest-friction move from self-hosted nexrender: identical mental model, zero machines. If your evaluation of nexrender ended at "the engine is right, the ops are not", start here before anywhere else.

Plainly#

Plainly is a metered SaaS render service: upload After Effects templates, connect data, and variations render in their cloud, from $69 per month as listed, metered by render minutes. It is a mature product with a developer-friendly API, and for a solo motion designer or a low-headcount shop with high render volume, paying by the render minute rather than by the seat is often the right economics. Since this article is about reading vendor content clearly, apply the same scepticism to everyone: Plainly publishes its own nexrender comparison pages, we publish this one, and you should run your own template through any tool before believing any of us. Our detailed views live at Nubu vs Plainly and the wider Plainly alternatives round-up.

Dataclay Templater#

Templater is the desktop veteran: an After Effects plugin that binds layers to rows in a data source and batch renders one output per row on your own machine. No cloud dependency at all, which some studios treat as a requirement rather than a limitation, and no code required, which makes it the classic choice for a motion designer who wants a render bot without becoming a developer. The ceiling is the desktop itself: renders occupy your machine, scale means more machines and more supervision, and review and delivery are whatever your studio already does around it. Pricing is on their site.

Nubu#

Nubu is the full-workflow entry, and ours, so weigh this section accordingly.

Where nexrender gives engineers an engine, Nubu gives teams the pipeline: the same genuine After Effects rendering, wrapped in the layers this review keeps pointing at. Templates are the .aep projects you already own, exported with the Nubu Builder plugin as ordinary template packages and uploaded to a shared library (templates overview, exporting your template). Campaigns are built on a node-based flow editor with live diagnostics, so problems surface while you build rather than at render time. CSV datasets run to 5,000 rows and 40 columns, and one build produces up to 5,000 creatives: the same flow and data always produce the same set.

The render farm underneath is the industrialised version of what a nexrender team assembles by hand, run entirely by Nubu: duplicate renders cannot happen, failures retry automatically, and every attempt keeps versioned outputs with full After Effects logs. Above it sits the part nexrender deliberately leaves out: builds land in review, teammates comment with @mentions, roles decide who approves, and approval is what queues the render (how a creative moves from build to render). On the Business+ plan, finished creatives deliver into Meta as paused ads and into Google Ads as paused Demand Gen ads and paused Performance Max asset groups, so a human always flips the final switch, and every ZIP export carries a media-buyer manifest CSV with all copy plus UTMs per creative.

Business+ also includes Nubu's AI campaign builder assistant, and nexrender has no equivalent. It drafts campaigns and whole flows as proposal cards that a human approves, and every flow it offers has already been test-built end to end, exactly as a real Build would run it, with the card showing the expected creative count and a matrix of real copy per row. It cannot render, publish, spend or delete, because those abilities do not exist for it, and it runs on your organisation's own OpenAI, Anthropic or Gemini key, billed by the provider at raw prices with no Nubu margin. The full write-up is at AI campaign builder for ads.

Honest limits, in the same spirit we have applied to everyone else: Nubu has no public API, so if you need renders inside your own software, nexrender is the better shaped tool, and delivery covers Meta and Google Ads only. Pricing is per-seat in GBP with VAT included: Free at £0 for one member with 10 GB, Starter at £29 per month plus £12 per seat, Pro at £79 plus £24, Business+ at £199 plus £39, with yearly billing saving 20% and no card needed for the trial. Details are on the pricing and features pages, and the direct head-to-head is at Nubu vs nexrender.

So, is nexrender good?#

Yes. It is well-designed software with an honest scope, and the fact that its fiercest reviews are written by companies selling replacements should not obscure that. The decision reduces to three questions.

Who touches the pipeline? Only engineers: nexrender, self-hosted if you want the machines, Nexrender Cloud if you do not. Engineers plus marketers, clients and approvers: a workflow product, and we would obviously suggest starting with ours; the trial needs no card.

Where must rendering live? Inside your own product: nexrender, no contest, because nothing else on this page embeds. Inside a tool your team logs into: any of the platforms above.

What are you optimising? Marginal cost per render at volume, with engineering time treated as already paid: self-hosted nexrender wins. Total cost including the software you would otherwise build around the engine: count the review UI, the approval chain and the delivery step before deciding, because that is where the real comparison lives.

However you land, run the test that no vendor content survives: take one real template and one real dataset, and push them through your shortlist end to end, from data to a file someone approved in the place it needed to reach. The tool that makes that whole journey shortest is the right one, whoever wrote the review.