Home

Add a Static Directory to an Eleventy Project

Copy static files from a directory into the root of the build directory with Eleventy.

Some static site generators, like Gatsby, have the concept of a static folder, in which anything you drop into that folder makes its way (unprocessed) to the build directory during the build process.

With Eleventy, a similar feature is trivial to achieve, but not so straightforward out of the box.

The simplest way to setup a static folder is to use the manual passthrough file copy. After reading the docs, it seems like it would be as simple as adding this code to your Eleventy config file:

.eleventy.js

module.exports = function (eleventyConfig) {
eleventyConfig.addPassthroughCopy("static");
};

But that would actually nest everything in static/ under _site/static/, assuming your output directory is _site (which is the default).

But what we really want is to copy everything in static directly to _site. To do that we can use an option in which we change the output directory. That code looks like this:

.eleventy.js

module.exports = function (eleventyConfig) {
eleventyConfig.addPassthroughCopy({ static: "/" });
};

This tells Eleventy to take everything in the static/ directory and copy it to the root of your build directory (e.g. static/sitemap.xml to _site/sitemap.xml).

Let's Connect

Keep Reading

Full-stack web development with 11ty

Frameworks like 11ty are only limited by the platforms to which you deploy them. Here we build a full-stack application by leveraging Netlify’s full-stack platform primitives.

Apr 11, 2025

2 Methods for Binding JavaScript Events with 11ty

When using raw JavaScript with 11ty, there are multiple approaches you can take for binding events, all without complicating the JavaScript you’re using.

Sep 29, 2022

JavaScript for 11ty with esbuild

As your 11ty application evolves, you’ll want more organization with your JavaScript. Here’s a method for bundling together using esbuild.

Sep 30, 2022