Note: This documentation is for version 1 of the Vercel platform. For the latest features, please see the version 2 documentation. If you have yet to upgrade, see the upgrade guide.

Static Builds

With Now, you can build static apps when deploying using a Dockerfile. You can build a static app however you wish and then output the content in a directory called /public for Now to upload after the build.

This works incredibly well with our GitHub integration. You can use this method to build your static apps and then deploy them automatically for review or staging. For example, see this pull request. For each and every push, you can access the built and deployed static app.


To build your static apps and deploy them on Now you'll need to create a Dockerfile that exports a static app to the /public directory. There must also be a now.json file with "type": "static" for Now to recognize that it should be built and deployed as a static app. Running now with this configuration will result in a static app built and deployed on Now.

Now let's take a look at a more in-depth example.

An example of building and deploying a Static Next.js App to Now

For this example, we are going to use a simple Next.js app that exports as static HTML.

Step 1: Preparing the app for export

First, let's look at how we would normally export a static app with Next.js in a local environment. We can use the following commands in a terminal, from the app directory, to export static HTML files from your Next.js app.

With Next.js, we can create npm scripts to help build and export our app. In this case, we'll want the following:

"scripts": {
  "build": "next build",
  "export": "next export"

Commands for building and exporting a static Next.js app. Read more about Next.js static exports.

npm run build
npm run export -- -o /public

With this, Next.js will build a static HTML app inside the `/public` directory, as we defined above in our `package.json`.

Step 2: Creating a Dockerfile

For Now to run our build and access our static app files to deploy, we'll need to create a Dockerfile. Within this file we can run the build process we defined in the previous step.

Let's look at the Dockerfile we would need to build our Next.js app statically.

FROM mhart/alpine-node

# Set the default working directory
WORKDIR /usr/src

# Install dependencies
COPY package.json package-lock.json ./
RUN npm i

# Copy the relevant files to the working directory
COPY . .

# Build and export the app
RUN npm run build && npm run export -o /public

A simple Dockerfile to build a Next.js app with Node.js and the package.json scripts we made in Step 1.

If you don't want to copy all of your files to the working directory, create a whitelist with a .dockerignore file.

Note that the Dockerfile gives the export script an option of -o /public. This is necessary because Now will use the contents of the /public directory as the content for the static deployment.

Step 3: Configuring Now for Static deployments

For Now to recognize our deployment as a static app, we'll need to mark it as a static type. To do this, we can add the following to the now.json configuration.

   "type": "static"

Setting `type` as `static` in a `now.json` file. Read more about configuring Now.

Please note that you can extend your now.json file as needed, but "type": "static" is required for static builds.

Although having a now.json is the preferred method for configuring your app deployments, you can also use the following with Vercel CLI:

now --static

Step 4: Building and Deploying

Finally, we can simply deploy our app by running the following command:


This will send the Dockerfile and the rest of our files to Now which will detect the Dockerfile and run it to build the app. This is thanks to setting the type of the deployment to be static. Now will then take the /public directory and then deploy it.

Once built and deployed, we can go to the deployment URL that Now gave us and see our static app live!

The above example is deployed to the following URL:

The above deployment is public so you can append /_src or /_logs to the URL to see the source of logs!

You can see the source code of the deployment here:

Make sure you have the latest version of the Vercel CLI to utilize static builds.
You can get it from

Whitelisting files for deployment with .dockerignore

‚ÄčNow will recognize a .dockerignore file to allow or disallow files to be deployed from your build.

Our recommendation is to create a .dockerignore file and utilizing it as a whitelist.

Let's take our first Next.js static app example. We can whitelist our package.json, package-lock.json, and pages directory with the following:


A `.dockerignore` file whitelisting basic Next.js files and directories.

With this file in place, Now will only deploy the files and directories we have listed. This is great to stop any accidentally placed or created files from being uploaded by mistake. We also make the build time shorter by uploading only the necessary files!

More Examples

With Docker, the possibilities for what we can build as a static app are endless. Let's take a look at a few more examples of what you can do with a Dockerfile and a static Now deployment.

Let's have a look at some more examples:


Here is an example of a simple Jekyll-based static app which uses a custom plugin. Unlike GitHub pages, where you cannot deploy since the plugin is not whitelisted, the Dockerfile we'll use compiles the Jekyll app at build time so we can use the plugin easily.

However, you can deploy this app inside Now without any issues. Here's the Dockerfile which builds the Jekyll app inside Now:

FROM ruby:2.5-alpine

# Set the default working directory
WORKDIR /usr/src

# Install some useful packages
RUN apk --no-cache add   zlib-dev   build-base   libxml2-dev   libxslt-dev   readline-dev   libffi-dev   yaml-dev   zlib-dev   libffi-dev   cmake

# Copy local files
COPY . .

# Build and export the app
RUN bundle install &&   bundle exec jekyll build --destination /public

A `Dockerfile` that utilizes Ruby and other packages to build a static Jekyll app and export it to `/public`

Take a look at the live example:

View the source code for the complete example:


create-react-app is a very popular React application project generator.

Let's take a look at using create-react-app with Docker and Node.js 10:

FROM mhart/alpine-node:10
WORKDIR /usr/src
COPY package-lock.json.lock package.json ./
RUN npm i
COPY . .
RUN npm run build && mv build /public

An example `Dockerfile` for building a `create-react-app` project to the `/public` directory

If you are using routing in your SPA don't forget to add a rewriting rule to point to your index.html. This can be done by editing now.json and adding the following block

"static": {
    "rewrites": [
        "source": "**",
        "destination": "/index.html"

An example of a rewrite rule to support SPA routing

Your own Continuous Integration

Static builds don't just mean that you have to export your app statically, it also presents a fantastic opportunity to run scripts that test your app too.

Even if you're using GitHub and have nothing to deploy in your repository, you can use Now + GitHub and a Dockerfile to run your own tests for each pull request.

Let's take a look at an example pull request using this method:

When someone pushes to that PR, Now will run tests inside that app and hosts the test report as a static app.

Here's the Dockerfile used inside that repo for the tests and deploying the report:

FROM alpine:3.5
RUN apk add --no-cache curl bash
WORKDIR /public
COPY . .
RUN bash ./
RUN echo "All tests passed!" > index.txt

A simple `Dockerfile` that runs a custom test script and prints the results to a text file ready to be deployed.

Using Environment Variables and Secrets

You can use a now.json configuration file and the now secrets command in tandem for use with the build step for static deployments.

Read more about how to configure them and use them.