ejs, handlebars, marko, and pug are server-side templating engines used to generate dynamic HTML in Node.js applications. They allow developers to embed data into HTML structures before sending the response to the client. While they share the same goal, they differ significantly in syntax philosophy, logic capabilities, and rendering performance. ejs uses standard JavaScript syntax within tags, handlebars enforces a logic-less approach with helpers, marko offers component-based async rendering, and pug relies on whitespace-sensitive indentation to reduce markup verbosity.
All four libraries solve the same core problem: generating HTML from data on the server. However, their philosophies on logic, syntax, and rendering performance vary widely. Let's compare how they handle common engineering challenges.
ejs embeds raw JavaScript directly into the template using tags.
<% %> blocks.<!-- ejs: Embedded JavaScript -->
<ul>
<% users.forEach(function(user) { %>
<li><%= user.name %></li>
<% }); %>
</ul>
handlebars enforces a logic-less approach using Mustache-style syntax.
#each or #if.<!-- handlebars: Logic-less -->
<ul>
{{#each users}}
<li>{{name}}</li>
{{/each}}
</ul>
marko uses a custom HTML-like syntax with built-in control flow tags.
<for> and <if> are part of the language, not helpers.<!-- marko: Custom control flow -->
<ul>
<for|user| of=data.users>
<li>${user.name}</li>
</for>
</ul>
pug relies on indentation and whitespace to define structure.
<!-- pug: Indentation-based -->
ul
each user in users
li= user.name
ejs uses "partials" which are just other EJS files included via include.
<!-- ejs: Include partial -->
<%- include('partials/header', { title: 'Home' }) %>
handlebars requires registering partials explicitly in your JS code before rendering.
Handlebars.registerPartial in your server code.{{> partialName }}.// handlebars: Register partial in JS
Handlebars.registerPartial('header', headerTemplateString);
<!-- handlebars: Use partial -->
{{> header title="Home" }}
marko treats every file as a component that can be imported.
import or <include> tags.<!-- marko: Component import -->
<import header from="./components/header.marko" />
<header title="Home" />
pug uses include or extends for layout inheritance.
extends allows defining blocks that child templates override.<!-- pug: Extend layout -->
extends layout.pug
block content
h1 Home
ejs is primarily synchronous in its basic API, though async functions can be awaited in templates (Node 8+).
ejs.render returns a string.// ejs: Synchronous render
const html = ejs.render(templateString, data);
res.send(html);
handlebars compiles templates to functions which are then executed.
{ knownHelpersOnly: false }).// handlebars: Compile then render
const template = Handlebars.compile(source);
const html = template(data);
res.send(html);
marko is built for async and streaming rendering from the ground up.
// marko: Async streaming
const template = require('./template.marko');
template.stream(data).pipe(res);
pug compiles templates to JavaScript functions.
res.render.// pug: Express integration
res.render('index', { users: users });
ejs escapes output by default when using `<%= %>.
<%- %> for raw, unescaped HTML (dangerous if data is untrusted).<!-- ejs: Escaping -->
<%= user.input %> <!-- Escaped -->
<%- user.richContent %> <!-- Raw (Unsafe) -->
handlebars escapes all expressions by default with {{ }}.
{{{ }}} are required for raw HTML.<!-- handlebars: Escaping -->
{{ user.input }} <!-- Escaped -->
{{{ user.richContent }}} <!-- Raw (Unsafe) -->
marko escapes all JavaScript output by default.
|html filter to output raw HTML.<!-- marko: Escaping -->
${ user.input } <!-- Escaped -->
${ user.richContent |html } <!-- Raw (Unsafe) -->
pug escapes interpolated variables by default.
!= for unescaped output.<!-- pug: Escaping -->
= user.input <!-- Escaped -->
!= user.richContent <!-- Raw (Unsafe) -->
While the syntax differs, these libraries share core architectural patterns.
// Shared concept: Render to string
// ejs
const html = ejs.render(template, data);
// handlebars
const html = template(data);
// marko
const html = marko.renderSync(template, data);
// pug
const html = pug.render(template, data);
// Shared concept: Passing data
const data = { title: "Home", user: "Alice" };
// All engines access 'title' and 'user' in the template
app.set('view engine', '...').// Shared concept: Express setup
app.set('view engine', 'ejs'); // or 'pug', 'handlebars', 'marko'
app.get('/', (req, res) => res.render('index'));
| Feature | ejs | handlebars | marko | pug |
|---|---|---|---|---|
| Syntax | 🟨 Embedded JS (<% %>) | 🟦 Logic-less ({{ }}) | 🟩 Custom Tags (<for>) | 🟪 Indentation (Whitespace) |
| Logic | ✅ Full JavaScript | ⚠️ Helpers Only | ✅ Built-in Control Flow | ✅ JavaScript Expressions |
| Rendering | 🔄 Sync (mostly) | 🔄 Sync (mostly) | ⚡ Async & Streaming | 🔄 Sync (mostly) |
| Security | 🔒 Manual Raw (<%-) | 🔒 Manual Raw ({{{) | 🔒 Manual Raw (` | html`) |
| Learning Curve | 📉 Low (JS knowledge) | 📈 Medium (New syntax) | 📈 High (Unique ecosystem) | 📉 Low (Clean syntax) |
ejs is the pragmatic choice 🛠️ for teams who want to leverage existing JavaScript skills without learning a new template language. It is widely supported and stable.
handlebars is the disciplined choice 📏 for projects that benefit from separating logic from views, such as email systems or designer-friendly templates.
marko is the performance choice 🚀 for high-scale applications where streaming and async rendering provide measurable latency improvements.
pug is the aesthetic choice 🎨 for developers who hate closing tags and want the cleanest possible markup, provided they can manage whitespace sensitivity.
Final Thought: For most standard Node.js web apps, ejs or pug offer the best balance of DX and capability. Choose handlebars for strict separation of concerns, and marko only if you have specific performance requirements that justify the learning curve.
Choose ejs if your team already knows JavaScript well and prefers minimal abstraction. It is ideal for simple server-rendered views where you want to use standard JS loops and conditionals without learning a new template syntax. It is also a safe choice for legacy Express applications that need stable, straightforward templating.
Choose handlebars if you want to enforce a separation between logic and view. It is excellent for email templates or scenarios where you need to restrict what designers can do in the template. Its helper system is robust, making it suitable for projects that require reusable logic without embedding full JavaScript.
Choose marko if performance is the top priority and you need async rendering out of the box. It is designed for high-scale applications (like eBay) where streaming HTML and component-based architecture on the server provide a tangible benefit. It requires buying into a more unique syntax and ecosystem.
Choose pug if you value clean, concise markup and don't mind whitespace-sensitive syntax. It is great for reducing HTML boilerplate significantly. However, ensure your team is comfortable with indentation-based structures, as mismatched tabs can cause hard-to-debug errors.
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.
<% %><%= %> (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.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.