ejs, handlebars, liquidjs, nunjucks, and pug are templating engines used to generate HTML on the server side within Node.js applications. They allow developers to embed dynamic data into static structures, reducing repetition and separating concerns between logic and presentation. While ejs and pug allow direct JavaScript execution, handlebars, liquidjs, and nunjucks enforce logic-less templates for better security and separation. Choosing the right engine depends on your security requirements, preferred syntax style, and need for template inheritance.
When building Node.js applications, you often need to generate HTML on the server. The ejs, handlebars, liquidjs, nunjucks, and pug packages all solve this problem, but they take very different approaches to syntax, security, and structure. Let's compare how they handle common templating tasks.
ejs embeds JavaScript directly inside standard HTML using angle brackets.
<!-- ejs: Standard HTML with JS tags -->
<div>
<h1><%= title %></h1>
<% if (showFooter) { %>
<footer>Copyright 2024</footer>
<% } %>
</div>
handlebars uses double mustaches for data and blocks for logic.
<!-- handlebars: Mustache syntax -->
<div>
<h1>{{title}}</h1>
{{#if showFooter}}
<footer>Copyright 2024</footer>
{{/if}}
</div>
liquidjs uses single braces for output and percent signs for logic.
<!-- liquidjs: Shopify-style syntax -->
<div>
<h1>{{ title }}</h1>
{% if showFooter %}
<footer>Copyright 2024</footer>
{% endif %}
</div>
nunjucks looks very similar to Liquid but with Jinja2 roots.
{% %} for logic and {{ }} for output.<!-- nunjucks: Jinja2-style syntax -->
<div>
<h1>{{ title }}</h1>
{% if showFooter %}
<footer>Copyright 2024</footer>
{% endif %}
</div>
pug removes HTML tags and uses indentation to define structure.
// pug: Whitespace-sensitive syntax
div
h1= title
if showFooter
footer Copyright 2024
ejs allows full JavaScript execution inside templates.
// ejs: Full JS logic
<% users.forEach(function(user) { %>
<li><%= user.name.toUpperCase() %></li>
<% }); %>
handlebars requires helpers for complex logic.
// handlebars: Helper-based logic
{{#each users}}
<li>{{toUpperCase this.name}}</li>
{{/each}}
// JS: Register helper
Handlebars.registerHelper('toUpperCase', (str) => str.toUpperCase());
liquidjs provides built-in filters for common transformations.
// liquidjs: Filter-based logic
{% for user in users %}
<li>{{ user.name | upcase }}</li>
{% endfor %}
nunjucks supports filters and custom extensions.
// nunjucks: Filter-based logic
{% for user in users %}
<li>{{ user.name | upper }}</li>
{% endfor %}
// JS: Add filter
env.addFilter('upper', (str) => str.toUpperCase());
pug allows JavaScript expressions but restricts statements.
each.// pug: Expression-based logic
each user in users
li= user.name.toUpperCase()
ejs relies on includes rather than true inheritance.
<!-- ejs: Includes -->
<%- include('partials/header') %>
<h1>Page Content</h1>
<%- include('partials/footer') %>
handlebars uses partials for reusable components.
<!-- handlebars: Partials -->
{{> header}}
<h1>Page Content</h1>
{{> footer}}
liquidjs uses sections and renders for layouts.
{% layout %} or {% render %} depending on version.<!-- liquidjs: Sections/Render -->
{% render 'header' %}
<h1>Page Content</h1>
{% render 'footer' %}
nunjucks has robust template inheritance with blocks.
<!-- nunjucks: Inheritance -->
{% extends "base.html" %}
{% block content %}
<h1>Page Content</h1>
{% endblock %}
pug supports extends and blocks natively.
// pug: Inheritance
extends base
block content
h1 Page Content
ejs executes arbitrary JavaScript code.
// ejs: Risky if user input reaches template
// <%= user.controlledInput %> could execute scripts if not escaped
// Use <%- %> carefully as it does not escape HTML
handlebars sandboxed by default.
// handlebars: Safe execution
// Template cannot access process.env or require()
// Only registered helpers are available
liquidjs designed for security first.
// liquidjs: Secure sandbox
// No arbitrary JS execution allowed
// Filters and tags are strictly defined
nunjucks restricts JavaScript execution.
// nunjucks: Restricted execution
// Templates cannot call arbitrary JS functions
// Security depends on custom filter implementation
pug compiles templates to JavaScript functions.
// pug: Compilation risk
// Template compiles to JS function
// User input must be sanitized before passing to render
While the syntax differs, these libraries share core goals and features.
// All packages support similar render methods
// ejs.render(template, data)
// hbs(template, data)
// liquid.parseAndRender(template, data)
// nunjucks.render(template, data)
// pug.renderFile(path, data)
// Common data passing pattern
const data = { title: 'Home', user: { name: 'Alice' } };
// Each engine maps these keys to template variables
// Example: Adding a date formatter
// ejs: Use a function in locals
// handlebars: RegisterHelper
// liquidjs: RegisterFilter
// nunjucks: AddFilter
// pug: Use mixins or functions
liquidjs and nunjucks have strong async stories.// Async rendering example
// await nunjucks.render('page.html', { fetchUser() });
// await liquid.parseAndRender(template, context);
// Express setup example
app.set('view engine', 'ejs'); // or hbs, liquid, nunjucks, pug
app.set('views', './views');
| Feature | Shared by All Engines |
|---|---|
| Core Goal | 🌐 Generate HTML from data |
| Data Passing | 🎨 Context objects / locals |
| Express Support | 📦 Built-in view engine integration |
| Custom Logic | 🛠️ Helpers, filters, or functions |
| Async Ready | ✅ Support asynchronous rendering |
| Feature | ejs / pug | handlebars / liquidjs / nunjucks |
|---|---|---|
| Logic | ⚙️ Full JS or Expressions | 🚫 Logic-less / Restricted |
| Syntax | 📝 HTML tags or Indentation | 🏷️ Mustache or Liquid tags |
| Security | ⚠️ Risky for user templates | 🔒 Sandboxed / Safe |
| Inheritance | 🧩 Includes / Blocks | 🏗️ Partials / Blocks / Sections |
| Best Use | 👨💻 Internal apps / Legacy | 🛒 E-commerce / User templates |
ejs and pug are like power tools 🔨 — they give you full control and speed but require caution. Ideal for internal dashboards, legacy Express apps, or teams that want to write JavaScript everywhere. Avoid them if users can edit templates.
handlebars, liquidjs, and nunjucks are like safety gear 🦺 — they restrict what can be done to prevent accidents. Perfect for SaaS platforms, e-commerce themes, or any app where users customize layouts. nunjucks offers the best inheritance, while liquidjs offers the best security model.
Final Thought: Security should drive your choice. If untrusted users touch templates, pick liquidjs or nunjucks. If it's all internal code, ejs or pug might save you time.
Choose ejs if you want a simple engine that lets you write plain JavaScript inside your templates. It is ideal for legacy Express applications or teams that prefer minimal abstraction over HTML. However, avoid it for user-generated templates because it allows arbitrary code execution. It works well when you need full access to JS utilities without writing custom helpers.
Choose handlebars if you need a logic-less template system with a strong ecosystem of helpers. It is widely used in email templating and static site generators where safety is critical. The syntax is verbose but clear, making it easy for non-developers to read. It requires registering helpers for complex logic, which enforces a clean separation of concerns.
Choose liquidjs if you need a secure, sandboxed engine compatible with Shopify themes. It is the best option for allowing users to edit templates without risking server security. The syntax is clean and familiar to many frontend developers. It supports async filters and tags, making it suitable for modern data fetching within templates.
Choose nunjucks if you want powerful template inheritance and macros similar to Python's Jinja2. It is excellent for large applications with complex layout hierarchies. The engine is fast and supports asynchronous rendering. It strikes a balance between flexibility and security by restricting direct JavaScript execution.
Choose pug if you prefer a whitespace-sensitive syntax that reduces HTML verbosity. It is great for teams that value concise code and don't mind the indentation requirements. However, it compiles to JavaScript functions, so it is not safe for user-edited templates. It works well for internal admin panels or projects where developer speed is prioritized over template safety.
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);
});
$ npm install ejs
Supports both CommonJS and ES Modules.
import ejs from 'ejs';
// Or
const ejs = require('ejs');
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.
<% %><%= %> (escape function configurable)<%- %>-%> ending tag<%_ _%>[? ?] instead of <% %>)<% if (user) { %>
<h2><%= user.name %></h2>
<% } %>
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.
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.
cache Compiled functions are cached, requires filenamefilename 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 contextcompileDebug When false no debug instrumentation is compileddelimiter 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 bodystrict 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 localsrmWhitespace 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.
<% '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 itFor the full syntax documentation, please see docs/syntax.md.
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 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>'
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.
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.
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') -%>
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.
<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>
Most of EJS will work as expected; however, there are a few things to note:
ejs.renderFile() won't work.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.
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
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
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.
VSCode:Javascript EJS by DigitalBrainstem
There are a number of implementations of EJS:
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.