A small tool that does one thing

Most static sites don't need a framework, a bundler config, and three build steps. They need a folder turned into clean files, with caching that works and images that aren't three times too large. That's the whole job Pagefold tries to do well.

Predictable by design

We care a lot about reproducibility. The same input folder produces the same output bytes every time, so a change in your dist directory always maps to a change you actually made. No hidden state, no surprise rebuilds.

Build the folder, read the summary, upload the result. If you ever have to think about the tool itself, we got something wrong.

Fast where it counts

Incremental builds mean a large site rebuilds only the pages you touched. Content hashing means repeat visitors download only what changed. Neither is a new idea — we just made them the default instead of an afternoon of configuration.

Where it runs

The output is plain files, so it runs wherever files run: a bucket, a static host, an edge cache in front of any of them. Pagefold never assumes a particular host and never phones home.

Thanks for reading. If you want the short version: point it at a folder, run one command, ship the result.