You can host a website for free in 2025. The two best approaches: use WordPress locally and export to a static site, or build with a modern static site generator. This guide compares both methods honestly.
The Two Approaches
| Approach | Tools | Best For |
|---|---|---|
| WordPress Static | WordPress Studio + Simply Static + Netlify | Non-developers, existing WP users |
| Astro + AI | Astro + Claude Code + Netlify | Developers, maximum control |
Both result in a fast, secure static site hosted free on Netlify. The path to get there differs significantly.
Approach 1: WordPress Studio + Static Export
What Is WordPress Studio?
WordPress Studio is a free desktop app from Automattic (the company behind WordPress.com) that runs WordPress locally on your computer.1 Released in April 2024, it eliminates the traditional complexity of local WordPress development.
Key Features:
- One-click WordPress installation
- No server configuration (no Apache, MySQL, etc.)
- Runs on SQLite (file-based, no database server)
- Built on WordPress Playground (WebAssembly)
- Available for Mac and Windows (Linux coming)
Step 1: Install WordPress Studio
- Download from developer.wordpress.com/studio1
- Install the application
- Click “Add Site” and name your project
- WordPress is ready in seconds
No terminal commands. No configuration files. No credentials to remember.
Step 2: Build Your Site Locally
With WordPress running locally, you can:
- Install any theme (free or premium)
- Add plugins for functionality
- Create pages and posts
- Customize with the block editor
- Test everything offline
Recommended Setup:
- Use a lightweight theme (GeneratePress, Kadence, Astra)
- Minimize plugins (each adds complexity to static export)
- Avoid plugins requiring server-side processing (contact forms, e-commerce)
Step 3: Install Simply Static Plugin
Simply Static converts your WordPress site to static HTML files.2
- In WordPress admin: Plugins → Add New
- Search “Simply Static”
- Install and activate
- Go to Simply Static → Settings
Configure Settings:
- Destination URL: Your Netlify URL (or custom domain)
- Delivery Method: Local Directory (for manual upload) or Netlify integration
- Include/Exclude: Remove unnecessary files
Step 4: Generate Static Files
- Go to Simply Static → Generate
- Click “Generate Static Files”
- Wait for the process to complete
- Download the ZIP file
Simply Static crawls your entire site, converting dynamic PHP pages to static HTML, CSS, and images.
Step 5: Deploy to Netlify
Option A: Manual Upload (Simplest)
- Go to app.netlify.com
- Sign up or log in (free)
- Drag and drop your ZIP file
- Site is live instantly
Option B: Git Integration
- Push static files to GitHub repository
- Connect repository to Netlify
- Automatic deploys on every push
What Works and What Doesn’t
Works Well:
- Brochure sites and portfolios
- Blogs and content sites
- Landing pages
- Documentation sites
Doesn’t Work:
- Contact forms (use Netlify Forms or Formspree)
- Search functionality (use Pagefind or Algolia)
- Comments (use Disqus or static alternatives)
- E-commerce (not suitable for static)
- User login/membership
Limitations of This Approach
- Plugin Compatibility: Many WordPress plugins won’t work after static export
- Update Workflow: Must regenerate and redeploy for every change
- No Dynamic Content: Comments, forms, search require external services
- Export Issues: Some themes/plugins cause export problems3
- Learning Curve: Still need to understand WordPress
Approach 2: Astro + Claude Code
What Is Astro?
Astro is a modern static site generator that outputs pure HTML with zero JavaScript by default.4 It’s designed for content-focused websites and delivers exceptional performance.
Key Features:
- Ships zero JavaScript by default
- Use React, Vue, Svelte components (optional)
- Built-in Markdown/MDX support
- Content collections for structured data
- Excellent developer experience
What Is Claude Code?
Claude Code is Anthropic’s AI coding assistant that runs in your terminal. It can write, edit, and explain code through natural language conversation.
Key Capabilities:
- Generate entire components from descriptions
- Debug and fix errors
- Refactor existing code
- Explain how things work
- Execute terminal commands
Step 1: Set Up Your Environment
Prerequisites:
- Node.js 18+ installed
- Git installed
- Code editor (VS Code recommended)
- Claude Code CLI (optional but powerful)
Create New Astro Project:
npm create astro@latest my-website
cd my-website
npm install
Choose your preferences during setup:
- Template: “Empty” or “Blog” for starters
- TypeScript: Recommended (optional)
- Strict: Yes for better code
Step 2: Build with Claude Code
With Claude Code, you describe what you want in plain English:
Example Prompts:
“Create a homepage with a hero section, three feature cards, and a footer”
“Add a blog with MDX support and a list of recent posts on the homepage”
“Style the site with a dark theme using CSS variables”
“Create a contact page with a form that uses Netlify Forms”
Claude Code generates the files, explains what it created, and can iterate based on feedback.
Step 3: Add Content
Markdown Files:
Create content in src/content/:
---
title: "My First Post"
pubDate: 2025-01-25
description: "Welcome to my blog"
---
Your content here in Markdown.
Content Collections: Astro validates your content with schemas, catching errors before they go live.
Step 4: Deploy to Netlify
Option A: Git Integration (Recommended)
- Push code to GitHub
- Connect to Netlify
- Netlify auto-detects Astro settings
- Every
git pushtriggers a new deploy
Option B: CLI Deploy
npm install -g netlify-cli
netlify deploy --prod
What Works and What Doesn’t
Works Well:
- Everything WordPress static does, plus more
- Complex layouts and components
- Full control over every element
- Server-side rendering (if needed)
- API integrations
- Dynamic islands of interactivity
Doesn’t Work (Without Additional Setup):
- WYSIWYG editing (need CMS integration)
- Non-technical content editors
- Real-time previews for non-developers
Head-to-Head Comparison
Setup Time
| Task | WordPress Studio | Astro + Claude |
|---|---|---|
| Initial setup | 5 minutes | 10-15 minutes |
| First page live | 30 minutes | 20-30 minutes |
| Learning curve | Lower (familiar UI) | Higher (code-based) |
| Full site | Hours to days | Hours to days |
Technical Requirements
| Requirement | WordPress Studio | Astro + Claude |
|---|---|---|
| Coding knowledge | None | Basic helpful, AI assists |
| Terminal usage | None | Required |
| Node.js | No | Yes |
| Git | Optional | Recommended |
Performance
| Metric | WordPress Static | Astro |
|---|---|---|
| Lighthouse score | 90-100 | 95-100 |
| JavaScript shipped | Depends on theme | Zero by default |
| Build time | Slower (crawls site) | Faster (direct build) |
| Page size | Larger (theme bloat) | Minimal |
Astro typically produces leaner output because you control every byte. WordPress themes often include unused CSS and JavaScript.
Flexibility
| Capability | WordPress Studio | Astro + Claude |
|---|---|---|
| Theme options | Thousands available | Build custom or use templates |
| Plugin ecosystem | Huge (but limited for static) | npm ecosystem |
| Custom functionality | Limited by plugins | Unlimited with code |
| Component libraries | Few | React, Vue, Svelte, etc. |
Content Editing
| Aspect | WordPress Studio | Astro |
|---|---|---|
| Visual editor | Yes (Gutenberg) | No (code/Markdown) |
| Non-technical friendly | Yes | No (without CMS) |
| Real-time preview | Yes | Dev server only |
| Content validation | No | Yes (schemas) |
Maintenance
| Task | WordPress Studio | Astro |
|---|---|---|
| Updates | WP core, themes, plugins | npm dependencies |
| Security | Keep WP updated locally | Minimal attack surface |
| Backups | Export files | Git history |
| Migration | Re-export and deploy | Push to new host |
Cost Comparison
Both approaches can be completely free:
WordPress Studio Path
| Item | Cost |
|---|---|
| WordPress Studio | Free |
| WordPress core | Free |
| Theme | Free (or $50-200 for premium) |
| Simply Static | Free (Pro: $99/year) |
| Netlify hosting | Free tier |
| Domain | $10-15/year (optional) |
| Total | $0-15/year |
Astro + Claude Code Path
| Item | Cost |
|---|---|
| Astro | Free |
| Claude Code | Free tier or $20/month for more usage |
| Netlify hosting | Free tier |
| Domain | $10-15/year (optional) |
| Total | $0-15/year (or +$20/month for heavy Claude usage) |
Which Should You Choose?
Choose WordPress Studio + Static If:
- You already know WordPress
- You want a visual editor
- You’re building a simple blog or brochure site
- You prefer clicking over coding
- You want access to WordPress themes
- You need to hand off to a non-technical client
Choose Astro + Claude Code If:
- You want maximum performance
- You’re comfortable with code (or willing to learn with AI help)
- You want full control over output
- You’re building something custom
- You plan to scale or add features later
- You want to learn modern web development
The Hybrid Option
You can also use a headless CMS with Astro for the best of both worlds:
- Content editing: Decap CMS, Tina CMS, or Sanity (visual editing)
- Site generation: Astro (performance and control)
- Hosting: Netlify (free)
This gives non-technical editors a familiar interface while developers maintain control over the frontend.
Step-by-Step: Quick Start for Each
WordPress Studio Quick Start
1. Download WordPress Studio
2. Create new site
3. Install theme and create content
4. Install Simply Static plugin
5. Generate static files
6. Drag ZIP to Netlify
7. Done - site is live
Astro + Claude Code Quick Start
# 1. Create project
npm create astro@latest my-site
# 2. Start development
cd my-site
npm run dev
# 3. Use Claude Code to build
# "Create a homepage with hero and features"
# 4. Add content in src/content/
# 5. Deploy to Netlify
netlify deploy --prod
# Done - site is live
Real-World Considerations
When WordPress Static Fails
I’ve seen WordPress static exports fail when:
- Plugins generate dynamic URLs
- Themes use heavy JavaScript
- Sites have thousands of pages (export takes forever)
- Forms or search are core features
When Astro Feels Overwhelming
Astro can feel complex when:
- You’ve never used a terminal
- You don’t understand HTML/CSS basics
- You need a site today with zero learning
- Your content team expects WordPress
The Honest Truth
WordPress Studio + Static is a clever workaround that makes WordPress work for static hosting. It’s not what WordPress was designed for, and you’ll occasionally fight that reality.
Astro was built for static sites from day one. Everything works as expected, but you’re writing code (even if AI helps significantly).
Neither is universally “better.” The right choice depends on your skills, timeline, and what you’re building.
Conclusion
Both approaches deliver the same end result: a fast, secure, free-hosted static website. The journey differs:
- WordPress Studio trades development complexity for export complexity
- Astro + Claude Code requires more upfront learning but provides cleaner output
For most developers or those willing to learn, Astro with AI assistance offers a more maintainable long-term solution. For WordPress users who want to keep their workflow, the static export path works—with caveats.
Try both. WordPress Studio takes minutes to test. Astro with Claude Code can have you productive in an afternoon. See which feels right for how you work.
Further Reading
- Related: Modern Tech Stack Guide
- Related: Hosting Platform Comparison
- WordPress Studio Documentation
- Astro Documentation
- Simply Static Plugin
- Netlify Astro Deploy Guide
References
Footnotes
-
Automattic. “WordPress Studio – Fast, Free Local Development.” https://developer.wordpress.com/studio/ ↩ ↩2
-
Simply Static. “The Best WordPress Static Site Generator.” https://simplystatic.com/ ↩
-
Netlify Support Forums. “WordPress Static Export Display Issues.” https://answers.netlify.com/t/wordpress-static-export-simply-static-wp2static-not-displaying-properly-when-uploaded-to-netlify/2364 ↩
-
Astro. “The web framework for content-driven websites.” https://astro.build/ ↩