FAQ

What is Publii?

Publii is a free, open-source desktop application for creating fast, secure static websites. It runs directly on your computer — Windows, Mac, or Linux — and works completely offline.

Think of it as WordPress without the complexity. You get the same visual interface for writing posts, managing pages, and customizing your site. But instead of building pages dynamically with databases and server code, Publii generates clean HTML files that you deploy to any hosting platform.

The result? Websites that load instantly, stay secure without constant updates, and cost almost nothing to host. You build everything locally on your machine, preview it before publishing, then push the finished files with one click.

How is Publii different from WordPress?

The biggest difference: Publii generates static HTML files while WordPress builds pages dynamically every time someone visits.

With WordPress, you need web hosting with PHP and MySQL. Your content lives in a database on a server. When someone visits your site, WordPress queries the database, processes PHP code, assembles the page, and sends it to the browser. This happens for every single page view.

Publii skips all that overhead. You work on your site locally on your computer. When you publish, Publii generates finished HTML files and uploads them to your host. No database. No server-side processing. Just clean files that load instantly.

What this means in practice:

• Speed — Publii sites load 3-5x faster because there's no database processing
• Security — No WordPress vulnerabilities to patch, no plugins to update, minimal attack surface
• Hosting — You can use free hosting like GitHub Pages or cheap CDN storage
• Offline work — Build your entire site without internet, publish when ready
• Privacy — No backend collecting visitor data, GDPR compliance built in

The tradeoff? WordPress offers more interactivity and dynamic features. But for content-focused sites — blogs, portfolios, business pages — Publii gives you everything you need with way less complexity.

Is Publii free?

Yes. Completely free, forever.

Publii is open-source software under the GPL-3.0 license. There are no premium versions, no paid upgrades, no hidden costs. Every feature is available to everyone. All future updates are free.

You don't even need paid hosting. Publii works with free platforms like GitHub Pages, Netlify. Or you can use affordable cloud storage like AWS S3 or Google Cloud. The choice is yours.

Can I use Publii offline?

Absolutely. That's one of Publii's biggest advantages.

Publii runs as a desktop application on your computer. You can write posts, edit pages, customize themes, and preview your entire site without any internet connection. Your content stays on your machine until you're ready to publish.

Internet is only needed when you deploy your site to a hosting platform. Everything else — writing, editing, designing, previewing — works completely offline. This makes Publii perfect for working on planes, in cafes with spotty WiFi, or anywhere you want privacy and control over your content.

What hosting options does Publii support?

Publii supports one-click deployment to multiple platforms:

• Amazon S3 — Industry-standard cloud storage with excellent performance
• Google Cloud Storage — Affordable CDN hosting with global distribution
• Netlify — Free tier with automatic deployments and custom domains
• GitHub Pages — Free hosting for static sites, perfect for personal projects
• GitLab Pages — Alternative to GitHub with built-in CI/CD
• FTP/SFTP — Any traditional web hosting that supports file uploads

You can also manually export your site and upload files to any host you want. Publii generates standard HTML files that work anywhere — no special server requirements needed.

Want to switch hosts? No problem. Just change your deployment settings and push to a new platform. Your site files are portable and host-agnostic.

Do I need coding knowledge to use Publii?

Nope. Publii is designed for anyone who can use WordPress or basic desktop software.

The interface gives you visual editors, drag-and-drop features, and settings panels with clear options. You write posts in a WYSIWYG, Block or Markdown editor — what you see is what you get. No markdown syntax. No terminal commands. No config files to edit.

That said, if you DO know HTML, CSS, or JavaScript, you can customize everything. Publii uses Handlebars templating, which is easy to learn and powerful for developers. But customization is optional — the available themes and tools work great out of the box.

Think of it like using Microsoft Word. Anyone can write a document. Power users can create complex templates. But you don't need to be a power user to get professional results.

What is a static site?

Think of a static site as a collection of ready-made web pages sitting on a server, waiting to be served. When someone visits your site, the server simply hands them the files — HTML, CSS, JavaScript — without building anything on the fly.

It's like having a printed book versus generating each page when someone asks to read it. Static sites use simple HTML, CSS, and JavaScript files that look the same for everyone. No databases, no server processing. Just clean, fast files served straight to your browser.

What kind of site can be created with a static website?

Static sites work great for blogs, portfolios, business websites, documentation, and landing pages. Basically anything where you're sharing information rather than running complex interactions. You know — the kind of sites where content matters more than real-time user features. If you're building the next Facebook with real-time chat and user-generated content? Probably not. But for 80% of websites out there? Static is perfect.

What are the differences and benefits between a dynamic and a static website?

Dynamic sites like WordPress build pages on demand using databases. They're flexible but need constant maintenance, security updates, and decent hosting. Static sites skip all that — pages are pre-built and just sit there waiting to be served. The result? Faster load times, lower costs, better security, and way less headache. The tradeoff is less interactivity, but honestly, most websites don't need database-driven content generation.

Want to explore the differences in more depth? See the full static vs dynamic CMS comparison.

What is a static CMS?

A static CMS gives you the content management experience you know from WordPress — writing posts, uploading images, customizing designs — but outputs static files instead of dynamic pages.

You work in a nice interface with visual editors and preview options. When you're ready to publish, the CMS generates clean HTML files and pushes them to your server. No databases to manage. No server-side code running on your host. Just fast, secure files.

Publii is a static CMS that runs right on your computer. You build your entire site offline, preview everything locally, then deploy finished files with one click. The result? WordPress-like simplicity with static site speed and security.

What are the differences between a Static Site Generator and Static Site CMS?

Both create static sites, but the experience is completely different.

Static Site Generators (like Jekyll or Hugo) are command-line tools for developers. You write content in markdown files, configure settings in YAML, run terminal commands to build your site. It's powerful if you're comfortable with code. If you're not? It's overwhelming.

Static CMS platforms give you buttons, editors, and visual tools. No terminal commands. No config files to debug. You manage everything through an interface — like using an app instead of writing scripts.

Think of it this way: Static Site Generators are like building furniture from raw materials. Static CMS is like IKEA — you still get to customize, but someone else handled the hard parts.

Privacy-focused website - what does it mean?

A privacy-focused website respects visitors by collecting minimal data and being transparent about what it does collect.

You're not tracking every click. Not selling visitor data to advertisers. Not using invasive analytics that follow people across the web. You use HTTPS for secure connections. You're clear about any data collection. And you follow regulations like GDPR not because you have to, but because it's the right thing to do.

In 2025, privacy isn't optional anymore. Visitors expect it. Regulations require it. And honestly, it's just good practice. Static sites make this easier because there's no backend collecting and storing user data by default.

Is a static CMS a good choice if you want a privacy-oriented website?

Absolutely. Static CMS platforms are naturally privacy-friendly because they don't need to collect user data to function.

There's no login system storing passwords. No database tracking visitor behavior. No server-side code processing personal information. You're just serving files — HTML, CSS, JavaScript — that display the same for everyone.

This makes GDPR compliance simpler. Less data collection means less risk, fewer disclosures, and easier regulatory compliance. If privacy matters to you or your audience, static is the obvious choice.

What does "serverless" mean?

Serverless doesn't mean no servers — it means you don't manage them. Your hosting provider handles all the infrastructure automatically, spinning up resources when needed and shutting them down when idle.

Traditional hosting means paying for a server that runs 24/7, whether you have zero visitors or 10,000. With serverless, you only pay for actual usage. Your site scales automatically based on traffic without you lifting a finger.

This is perfect for sites with unpredictable traffic. Maybe you get featured on Reddit and suddenly have 50,000 visitors. Serverless handles it. The next day traffic drops back to normal? Costs drop too. The cloud manages everything — you just focus on content.

What is Headless technology?

Headless technology separates your website's frontend (what visitors see) from the backend (where content and logic live). They operate independently but communicate through APIs when needed.

This separation gives you incredible flexibility. You can have a static frontend for blazing speed and security while still pulling in dynamic features when necessary. Need to add e-commerce? Integrate Shopify's API. Want user comments? Connect a service like Disqus. Need a contact form? Use a serverless function.

Your site stays fast and secure because the core is static, but you can layer on dynamic features exactly where you need them. It's like having a lightweight sports car that can tow a trailer when necessary — performance when you want it, capabilities when you need them.