ejs vs handlebars vs jade vs mustache vs nunjucks vs pug
Server-Side Template Engines for Node.js Applications
ejshandlebarsjademustachenunjuckspug

Server-Side Template Engines for Node.js Applications

ejs, handlebars, jade (deprecated), mustache, nunjucks, and pug are template engines used to generate HTML dynamically on the server side in Node.js environments. They allow developers to embed logic, iterate over data, and include partials within HTML structures, separating presentation from business logic. While jade has been renamed to pug, the legacy package remains in the ecosystem, often causing confusion. mustache and handlebars focus on logic-less templating, whereas ejs and nunjucks allow JavaScript-like expressions. pug offers a whitespace-sensitive syntax that reduces boilerplate. Choosing the right engine depends on your team's familiarity with HTML vs. indentation-based syntax, the need for logic within templates, and long-term maintenance considerations.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
ejs08,117211 kB272 months agoApache-2.0
handlebars018,6512.81 MB1104 months agoMIT
jade021,854-33211 years agoMIT
mustache016,727-1175 years agoMIT
nunjucks08,9761.77 MB3553 years agoBSD-2-Clause
pug021,85422.5 kB3324 months agoMIT

Server-Side Template Engines: ejs, handlebars, mustache, nunjucks, pug (and the legacy jade)

When building Node.js applications, rendering HTML on the server remains a common requirement for SEO, initial load performance, or simple email generation. The ecosystem offers several mature template engines, each with a distinct philosophy on syntax, logic, and extensibility. This comparison breaks down ejs, handlebars, mustache, nunjucks, and pug — while also addressing the deprecated jade package — to help you make an informed architectural choice.

⚠️ Critical Note: The Status of jade

Before diving into features, we must address jade. The jade templating engine was renamed to pug in 2016 due to trademark issues. The jade package on npm is deprecated and no longer receives security updates or bug fixes.

// ❌ DO NOT USE: Legacy jade package
const jade = require('jade'); 
// This package is unmaintained and may contain vulnerabilities
// ✅ USE THIS: Modern pug package
const pug = require('pug');
// Actively maintained, same syntax as jade but safer

If you are starting a new project, never install jade. If you are maintaining legacy code, plan a migration to pug. For the rest of this comparison, we will treat pug as the representative for the indentation-based syntax family.

📝 Syntax Style: HTML-like vs. Whitespace-Sensitive

The most immediate difference developers notice is the syntax. Some engines look like HTML with extra tags, while others use indentation to define structure.

ejs uses standard HTML with JavaScript embedded between <% %> tags. It feels familiar to anyone who has written PHP or ASP.

<!-- ejs: HTML-like syntax -->
<ul>
  <% users.forEach(function(user) { %>
    <li><%= user.name %></li>
  <% }); %>
</ul>

handlebars also uses HTML-like syntax but relies on double mustaches {{ }} for expressions and blocks.

<!-- handlebars: Block expressions -->
<ul>
  {{#each users}}
    <li>{{name}}</li>
  {{/each}}
</ul>

mustache is similar to Handlebars but strictly logic-less, using the same {{ }} syntax.

<!-- mustache: Logic-less sections -->
<ul>
  {{#users}}
    <li>{{name}}</li>
  {{/users}}
</ul>

nunjucks uses HTML-like syntax with {% %} for control flow and {{ }} for variables, inspired by Python's Jinja2.

<!-- nunjucks: Jinja2-style blocks -->
<ul>
  {% for user in users %}
    <li>{{ user.name }}</li>
  {% endfor %}
</ul>

pug (formerly jade) uses a whitespace-sensitive syntax that omits closing tags and angle brackets, resulting in less code.

// pug: Indentation-based syntax
ul
  each user in users
    li= user.name

🧠 Logic Capabilities: JavaScript vs. Logic-Less

A key architectural decision is how much logic you allow in your views. Some teams prefer strict separation, while others value the convenience of helper functions inside templates.

ejs allows full JavaScript execution inside templates. You can write loops, conditionals, and even define functions directly in the view.

<!-- ejs: Full JavaScript support -->
<% if (user.role === 'admin') { %>
  <p>Welcome, Administrator!</p>
<% } else { %>
  <p>Hello, User.</p>
<% } %>

handlebars is logic-less by design. You cannot write arbitrary JavaScript. You must use built-in helpers or register custom ones.

<!-- handlebars: Custom helpers required for logic -->
{{#if (eq user.role "admin")}}
  <p>Welcome, Administrator!</p>
{{else}}
  <p>Hello, User.</p>
{{/if}}

mustache is strictly logic-less. It supports sections and inverted sections but no custom helpers or arbitrary logic.

<!-- mustache: Inverted sections for else logic -->
{{#isAdmin}}
  <p>Welcome, Administrator!</p>
{{/isAdmin}}
{{^isAdmin}}
  <p>Hello, User.</p>
{{/isAdmin}}

nunjucks allows some logic but keeps it contained within its own template language. It supports filters and custom extensions.

<!-- nunjucks: Template-specific logic -->
{% if user.role == 'admin' %}
  <p>Welcome, Administrator!</p>
{% else %}
  <p>Hello, User.</p>
{% endif %}

pug allows JavaScript expressions but encourages keeping logic minimal. It supports mixins for reusable blocks.

// pug: JavaScript expressions in attributes
if user.role == 'admin'
  p Welcome, Administrator!
else
  p Hello, User.

🧩 Reusability: Partials, Includes, and Inheritance

Large applications require modular templates. Engines handle reuse differently, from simple includes to full template inheritance.

ejs supports includes via <%- include() %> but lacks native template inheritance. You often need to wrap layouts manually.

<!-- ejs: Simple includes -->
<%- include('partials/header') %>
<h1>Home Page</h1>
<%- include('partials/footer') %>

handlebars supports partials and block helpers, allowing for modular components.

<!-- handlebars: Partials -->
{{> header}}
<h1>Home Page</h1>
{{> footer}}

mustache supports partials using the > syntax.

<!-- mustache: Partials -->
{{> header}}
<h1>Home Page</h1>
{{> footer}}

nunjucks has powerful template inheritance using {% extends %} and {% block %}, similar to Django or Jinja2.

<!-- nunjucks: Template inheritance -->
{% extends "layout.html" %}
{% block content %}
  <h1>Home Page</h1>
{% endblock %}

pug supports both includes and extends, offering a clean syntax for inheritance.

// pug: Extends and blocks
extends layout

block content
  h1 Home Page

🚀 Async Rendering and Performance

Modern applications often need to fetch data during rendering. Not all engines handle asynchronous operations within templates equally.

ejs does not support async functions inside templates natively. You must resolve all data before passing it to the render function.

// ejs: Data must be resolved beforehand
const html = ejs.render(template, { users: await fetchUsers() });

handlebars supports async helpers in recent versions, allowing data fetching within the template context.

// handlebars: Async helpers possible
Handlebars.registerHelper('fetchUser', async (id) => {
  return await getUser(id);
});

mustache does not support async rendering. All data must be prepared in advance.

// mustache: Synchronous only
const output = Mustache.render(template, view);

nunjucks supports async rendering natively, allowing filters and functions to return promises.

// nunjucks: Async support enabled
nunjucks.render('page.html', { users: fetchUsers() }, (err, res) => {
  // Handles promises internally
});

pug supports async functions in mixins and includes when configured properly.

// pug: Async mixins
pug.renderFile('view.pug', { async: true }, (err, html) => {
  // Can handle async operations within template
});

🛡️ Security: Escaping and XSS Prevention

Security is critical when rendering user-generated content. All major engines provide escaping mechanisms, but defaults vary.

ejs escapes output by default when using <%= %> but allows unescaped output with <%- %>, which can be dangerous if misused.

<!-- ejs: Escaped vs Unescaped -->
<%= userInput %>   <!-- Escaped automatically -->
<%- userInput %>   <!-- Raw HTML (XSS risk if userInput is untrusted) -->

handlebars escapes expressions by default using {{ }}. Use triple mustaches {{{ }}} for raw HTML.

<!-- handlebars: Escaping -->
{{userInput}}   <!-- Escaped -->
{{{userInput}}} <!-- Raw HTML -->

mustache escapes by default. Use {{{ }}} for unescaped content.

<!-- mustache: Escaping -->
{{userInput}}   <!-- Escaped -->
{{{userInput}}} <!-- Raw HTML -->

nunjucks escapes by default. Use the safe filter to bypass escaping.

<!-- nunjucks: Escaping -->
{{ userInput }}      <!-- Escaped -->
{{ userInput | safe }} <!-- Raw HTML -->

pug escapes interpolated values by default. Use ! prefix for unescaped output.

// pug: Escaping
p= userInput   // Escaped
p!= userInput  // Raw HTML

📊 Summary: Key Differences

Featureejshandlebarsmustachenunjuckspug
SyntaxHTML + JS tagsHTML + {{ }}HTML + {{ }}HTML + {% %}Indentation
LogicFull JavaScriptHelpers onlyNoneTemplate logicExpressions
InheritanceManual (includes)PartialsPartialsExtends/BlocksExtends/Blocks
AsyncNoYes (helpers)NoYesYes
StatusMaintainedMaintainedMaintainedMaintainedMaintained

💡 The Big Picture

ejs is the pragmatic choice for teams who want zero learning curve. If your developers know JavaScript and HTML, they know EJS. It is perfect for simple views, email templates, or quick prototypes where strict separation of concerns is less critical.

handlebars is the balanced choice. It enforces cleaner views than EJS without being as restrictive as Mustache. Its ecosystem of helpers and partials makes it a robust standard for many Express applications.

mustache is the portable choice. Because it is logic-less and implemented in many languages, you can share templates between client and server or across different backend services. Use it when consistency across platforms matters more than convenience.

nunjucks is the power-user choice. If you are coming from Python/Django or need complex template inheritance and async features, Nunjucks offers the most capability. It is excellent for large content-heavy sites.

pug is the productivity choice. Its concise syntax reduces file size and typing. It is ideal for teams that prefer indentation-based languages (like Python or YAML) and want to write less boilerplate HTML.

Final Thought: Avoid jade entirely. For new projects, handlebars and pug are the most common modern choices. Pick handlebars if you want standard HTML structure, or pug if you want to write less code. Choose nunjucks if you need advanced template features, and ejs if you want simplicity above all.

How to Choose: ejs vs handlebars vs jade vs mustache vs nunjucks vs pug

  • ejs:

    Choose ejs if you want a simple, JavaScript-native templating syntax that feels like writing standard HTML with embedded JS. It is ideal for teams that prefer minimal abstraction and want to use existing JavaScript knowledge without learning a new DSL. It works well for small to medium projects where complex template inheritance is not required.

  • handlebars:

    Choose handlebars if you need a logic-less template engine that enforces a clear separation between view and controller logic. It is suitable for projects that require robust partials, helpers, and a mature ecosystem with strong community support. It strikes a balance between simplicity and power, making it a safe default for many Express applications.

  • jade:

    Do NOT choose jade for new projects. The jade package was renamed to pug in 2016 and the original jade npm package is deprecated and no longer maintained. Using it introduces security risks and compatibility issues. If you encounter legacy code using jade, plan a migration to pug or another modern engine.

  • mustache:

    Choose mustache if you need a language-agnostic, logic-less templating system that can be shared across frontend and backend environments. It is best for scenarios where you want to guarantee no business logic leaks into views, as it strictly prohibits if/else blocks or custom helpers without pre-processing. It is lightweight and portable.

  • nunjucks:

    Choose nunjucks if you want a powerful, feature-rich engine inspired by Jinja2 with support for inheritance, macros, and asynchronous rendering. It is ideal for large-scale applications where template organization, reuse, and complex logic within views are necessary. It offers the most flexibility among the logic-allowing engines.

  • pug:

    Choose pug if you prefer a concise, whitespace-sensitive syntax that reduces HTML verbosity and speeds up writing views. It is well-suited for teams that value clean, indentation-based code and want built-in support for mixins, filters, and template inheritance. It is the modern successor to jade and is actively maintained.

README for ejs

Embedded JavaScript templates
Known Vulnerabilities

Security

Security professionals, before reporting any security issues, please reference the SECURITY.md in this project, in particular, the following: "EJS is effectively a JavaScript runtime. Its entire job is to execute JavaScript. If you run the EJS render method without checking the inputs yourself, you are responsible for the results."

In short, DO NOT submit 'vulnerabilities' that include this snippet of code:

app.get('/', (req, res) => {
  res.render('index', req.query);
});

Installation

$ npm install ejs

Import or require

Supports both CommonJS and ES Modules.

import ejs from 'ejs';
// Or
const ejs = require('ejs');

Compatibility

Server: CommonJS approach (require) supports Node versions at least back to v0.12, likely older versions too. ES Modules approach (import) requires a Node version that supports ESM.

CLI: Requires Node v8 or newer.

Browser: EJS supports all modern browsers, but is very likely to work even in very, very old browsers. Your mileage may vary.

Bundlers and alternate runtimes: as of v6.0, the published package imports cleanly under Rollup, Rolldown, tsdown, esbuild, Webpack, Vite, Browserify, Bun, and Deno. Earlier versions emitted module.exports = ejs; from inside the ESM source as a dual-mode shim; modern ESM-aware bundlers and Bun treated this as malformed ESM. The shim has been removed from lib/esm/*.js and moved into the lib/cjs/* compile step, so the published CJS surface (require('ejs')) is unchanged. For Browserify, pass --node so it picks the main entry instead of the prebuilt UMD bundle pointed to by the browser field.

Features

  • Control flow with <% %>
  • Escaped output with <%= %> (escape function configurable)
  • Unescaped raw output with <%- %>
  • Newline-trim mode ('newline slurping') with -%> ending tag
  • Whitespace-trim mode (slurp all whitespace) for control flow with <%_ _%>
  • Custom delimiters (e.g. [? ?] instead of <% %>)
  • Includes
  • Client-side support
  • Static caching of intermediate JavaScript
  • Static caching of templates
  • Complies with the Express view system

Example

<% if (user) { %>
  <h2><%= user.name %></h2>
<% } %>

Basic usage

const template = ejs.compile(str, options);
template(data);
// => Rendered HTML string

ejs.render(str, data, options);
// => Rendered HTML string

ejs.renderFile(filename, data, options, function(err, str){
    // str => Rendered HTML string
});

It is also possible to use ejs.render(dataAndOptions); where you pass everything in a single object. In that case, you'll end up with local variables for all the passed options. However, be aware that your code could break if we add an option with the same name as one of your data object's properties. Therefore, we do not recommend using this shortcut.

Important

You should never give end-users unfettered access to the EJS render method, If you do so you are using EJS in an inherently un-secure way.

Options

  • cache Compiled functions are cached, requires filename
  • filename The name of the file being rendered. Not required if you are using renderFile(). Used by cache to key caches, and for includes.
  • root Set template root(s) for includes with an absolute path (e.g, /file.ejs). Can be array to try to resolve include from multiple directories.
  • views An array of paths to use when resolving includes with relative paths.
  • context Function execution context
  • compileDebug When false no debug instrumentation is compiled
  • delimiter Character to use for inner delimiter, by default '%'
  • openDelimiter Character to use for opening delimiter, by default '<'
  • closeDelimiter Character to use for closing delimiter, by default '>'
  • debug Outputs generated function body
  • strict When set to true, generated function is in strict mode
  • _with Whether or not to use with() {} constructs. If false then the locals will be stored in the locals object. Set to false in strict mode.
  • unsafePrototypeLocals When true, allows templates to resolve identifiers through the prototype chain of the locals object. Required if you pass class instances or Object.create(...) results as locals and rely on inherited properties at the top level. Defaults to false; enabling it disables the v6 prototype-pollution mitigation.
  • destructuredLocals An array of local variables that are always destructured from the locals object, available even in strict mode.
  • localsName Name to use for the object storing local variables when not using with Defaults to locals
  • rmWhitespace Remove all safe-to-remove whitespace, including leading and trailing whitespace. It also enables a safer version of -%> line slurping for all scriptlet tags (it does not strip new lines of tags in the middle of a line).
  • escape The escaping function used with <%= construct. (By default escapes XML).
  • outputFunctionName Set to a string (e.g., 'echo' or 'print') for a function to print output inside scriptlet tags.
  • async When true, EJS will use an async function for rendering. (Depends on async/await support in the JS runtime).
  • includer Custom function to handle EJS includes, receives (originalPath, parsedPath) parameters, where originalPath is the path in include as-is and parsedPath is the previously resolved path. Should return an object { filename, template }, you may return only one of the properties, where filename is the final parsed path and template is the included content.

This project uses JSDoc. For the full public API documentation, clone the repository and run jake doc. This will run JSDoc with the proper options and output the documentation to out/. If you want the both the public & private API docs, run jake devdoc instead.

Tags

  • <% 'Scriptlet' tag, for control-flow, no output
  • <%_ 'Whitespace Slurping' Scriptlet tag, strips all whitespace before it
  • <%= Outputs the value into the template (escaped)
  • <%- Outputs the unescaped value into the template
  • <%# Comment tag, no execution, no output
  • <%% Outputs a literal '<%'
  • %%> Outputs a literal '%>'
  • %> Plain ending tag
  • -%> Trim-mode ('newline slurp') tag, trims following newline
  • _%> 'Whitespace Slurping' ending tag, removes all whitespace after it

For the full syntax documentation, please see docs/syntax.md.

Includes

Includes either have to be an absolute path, or, if not, are assumed as relative to the template with the include call. For example if you are including ./views/user/show.ejs from ./views/users.ejs you would use <%- include('user/show') %>.

You must specify the filename option for the template with the include call unless you are using renderFile().

You'll likely want to use the raw output tag (<%-) with your include to avoid double-escaping the HTML output.

<ul>
  <% users.forEach(function(user){ %>
    <%- include('user/show', {user: user}) %>
  <% }); %>
</ul>

Includes are inserted at runtime, so you can use variables for the path in the include call (for example <%- include(somePath) %>). Variables in your top-level data object are available to all your includes, but local variables need to be passed down.

NOTE: Include preprocessor directives (<% include user/show %>) are not supported in v3.0+.

Custom delimiters

Custom delimiters can be applied on a per-template basis, or globally:

import ejs from 'ejs';
const users = ['geddy', 'neil', 'alex'];

// Just one template
ejs.render('<p>[?= users.join(" | "); ?]</p>', {users: users}, {delimiter: '?', openDelimiter: '[', closeDelimiter: ']'});
// => '<p>geddy | neil | alex</p>'

// Or globally
ejs.delimiter = '?';
ejs.openDelimiter = '[';
ejs.closeDelimiter = ']';
ejs.render('<p>[?= users.join(" | "); ?]</p>', {users: users});
// => '<p>geddy | neil | alex</p>'

Caching

EJS ships with a basic in-process cache for caching the intermediate JavaScript functions used to render templates. It's easy to plug in LRU caching using Node's lru-cache library:

import ejs from 'ejs';
import { LRUCache } from 'lru-cache';

ejs.cache = LRUCache({max: 100}); // LRU cache with 100-item limit

If you want to clear the EJS cache, call ejs.clearCache. If you're using the LRU cache and need a different limit, simple reset ejs.cache to a new instance of the LRU.

Custom file loader

The default file loader is fs.readFileSync, if you want to customize it, you can set ejs.fileLoader.

import ejs from 'ejs';

const myFileLoad = function (filePath) {
  return 'myFileLoad: ' + fs.readFileSync(filePath);
};

ejs.fileLoader = myFileLoad;

With this feature, you can preprocess the template before reading it.

Layouts

EJS does not specifically support blocks, but layouts can be implemented by including headers and footers, like so:

<%- include('header') -%>
<h1>
  Title
</h1>
<p>
  My page
</p>
<%- include('footer') -%>

Client-side support

Go to the Latest Release, download ./ejs.js or ./ejs.min.js. Alternately, you can compile it yourself by cloning the repository and running jake build (or npx jake build if jake is not installed globally).

Include one of these files on your page, and ejs should be available globally.

Example

<div id="output"></div>
<script src="ejs.min.js"></script>
<script>
  let people = ['geddy', 'neil', 'alex'],
      html = ejs.render('<%= people.join(", "); %>', {people: people});
  // With jQuery:
  $('#output').html(html);
  // Vanilla JS:
  document.getElementById('output').innerHTML = html;
</script>

Caveats

Most of EJS will work as expected; however, there are a few things to note:

  1. Obviously, since you do not have access to the filesystem, ejs.renderFile() won't work.
  2. For the same reason, includes do not work unless you use an include callback. Here is an example:
let str = "Hello <%= include('file', {person: 'John'}); %>",
    fn = ejs.compile(str);

fn(data, null, function(path, d){ // include callback
  // path -> 'file'
  // d -> {person: 'John'}
  // Put your code here
  // Return the contents of file as a string
}); // returns rendered string

See the examples folder for more details.

CLI

EJS ships with a full-featured CLI. Options are similar to those used in JavaScript code:

  • -o / --output-file FILE Write the rendered output to FILE rather than stdout.
  • -f / --data-file FILE Must be JSON-formatted. Use parsed input from FILE as data for rendering.
  • -i / --data-input STRING Must be JSON-formatted and URI-encoded. Use parsed input from STRING as data for rendering.
  • -m / --delimiter CHARACTER Use CHARACTER with angle brackets for open/close (defaults to %).
  • -p / --open-delimiter CHARACTER Use CHARACTER instead of left angle bracket to open.
  • -c / --close-delimiter CHARACTER Use CHARACTER instead of right angle bracket to close.
  • -s / --strict When set to true, generated function is in strict mode
  • -n / --no-with Use 'locals' object for vars rather than using with (implies --strict).
  • -l / --locals-name Name to use for the object storing local variables when not using with.
  • -w / --rm-whitespace Remove all safe-to-remove whitespace, including leading and trailing whitespace.
  • -d / --debug Outputs generated function body
  • -h / --help Display this help message.
  • -V/v / --version Display the EJS version.

Here are some examples of usage:

$ ejs -p [ -c ] ./template_file.ejs -o ./output.html
$ ejs ./test/fixtures/user.ejs name=Lerxst
$ ejs -n -l _ ./some_template.ejs -f ./data_file.json

Data input

There is a variety of ways to pass the CLI data for rendering.

Stdin:

$ ./test/fixtures/user_data.json | ejs ./test/fixtures/user.ejs
$ ejs ./test/fixtures/user.ejs < test/fixtures/user_data.json

A data file:

$ ejs ./test/fixtures/user.ejs -f ./user_data.json

A command-line option (must be URI-encoded):

./bin/cli.js -i %7B%22name%22%3A%20%22foo%22%7D ./test/fixtures/user.ejs

Or, passing values directly at the end of the invocation:

./bin/cli.js -m $ ./test/fixtures/user.ejs name=foo

Output

The CLI by default send output to stdout, but you can use the -o or --output-file flag to specify a target file to send the output to.

IDE Integration with Syntax Highlighting

VSCode:Javascript EJS by DigitalBrainstem

Related projects

There are a number of implementations of EJS:

License

Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)


EJS Embedded JavaScript templates copyright 2112 mde@fleegix.org.