FAQ and troubleshooting

Answers to common questions about the templates, and fixes for common problems with forms, dark mode, hosting and installs.

Are the templates really free?#

Most of them, yes. Free templates are released under the MIT License: use them for personal or commercial sites and client work, with no attribution required. Premium templates, marked Premium on the site, are sold instead: buying one gives you the Freeframe Commercial License for it, and All-access covers every premium template at once. See the license.

Do I need to know Tailwind or React?#

No. The HTML versions work as plain files; you only need Node.js to rebuild the CSS after adding new Tailwind classes. The Next.js versions are for people who already use React. The Astro versions need no React either: their components are close to HTML.

Should I pick the Next.js or the Astro version?#

Both have the same pages, design and features. Pick Astro for a fast, mostly static site with very little JavaScript, especially if you'll add a blog or other Markdown content. Pick Next.js if you work with React or plan to add server features such as API routes, accounts or a database. See Choosing a stack.

Do I need to code to use the WordPress version?#

No. Every page is made of blocks that you edit in the WordPress editor, and colours and fonts are in Appearance > Editor > Styles. Interactive parts such as forms, filters and calculators are kept in Custom HTML blocks; their documentation explains what you can change safely.

A class I added has no effect#

Tailwind only generates CSS for classes it has seen. In an HTML template, run npm run build (or npm run watch while editing). In Next.js, check the dev server is running and that the class is written in full, not assembled from pieces of a string.

My form says it was sent, but nothing arrived#

The forms don't send anything until you connect them. See Forms and backends.

The og:image URL must be absolute (https://example.com/...), point to a PNG or JPG, and be reachable publicly. See SEO and social images.

Pages work locally but not on my host#

Upload the whole folder, keeping its structure; paths are relative.
For Next.js, upload the contents of out/ after pnpm build, not the project folder.
If your site lives in a sub-folder (for example GitHub Pages project sites), build the Next.js version with DEMO_BASE_PATH=/your-folder.

Dark mode flashes or doesn't remember the choice#

The theme script must stay in the <head> (HTML) or root layout (Next.js) so it runs before the page paints. If you moved or deferred it, put it back.

Saved data looks wrong after I changed a template#

Templates that remember things (a cart, favourites, saved progress) keep them in your browser's localStorage, and check the data whenever they read it. After changing the data structure, clear the site's storage in your browser's developer tools, or change the storage key.

`pnpm install` fails on a Next.js or Astro template#

Use Node.js 24 (node -v). If pnpm asks to approve build scripts, approve the ones listed in the template's pnpm-workspace.yaml. npm works too: npm install, then npm run dev.