Guide
How much does a church website cost?
The honest ranges for 2026, what actually drives the price, and the fees you should never agree to.
It is the first question almost every church office asks me, and it deserves a straight answer: a church website in 2026 costs anywhere from nothing to well over ten thousand dollars, and the number depends far less on how many pages you have than on who keeps it up to date after it launches. Here is how the ranges actually break down.
The short answer
There are four common paths, and each one is a reasonable choice for a different church. The prices below are typical for 2026, in US dollars.
| Approach | Typical 2026 cost | A good fit when |
|---|---|---|
| Do it yourself on a builder | $0 - $30 / month | You are tiny, on a shoestring, and have a volunteer who likes this work. |
| Freelancer with a template | $500 - $2,500 one-time | You want it to look decent and do not need much beyond the basics. |
| Professional custom site | $2,500 - $6,000+ one-time | You want it fast, findable, accessible, and easy for staff to edit. |
| Full agency | $10,000+ | You are a large multi-site church with staff to manage the relationship. |
Most single-congregation churches land in the middle two rows. The jump from a template to a custom site is not really about looks. It is about speed on a phone, showing up correctly in Google and Maps, and whether your office can change a service time without emailing a developer.
What actually drives the price
A handful of things move the number up or down. In rough order of impact:
- Who edits it after launch. A site anyone on staff can update is worth more to build and worth every penny later. A site only a developer can touch is cheaper up front and expensive forever.
- How many real pages you need. One strong page costs less than a full site with About, Beliefs, Ministries, Events, and a sermon archive.
- Custom design versus a template. A template is faster and cheaper; a design built around your congregation costs more and lasts longer.
- Bilingual content. Running the site in English and Spanish from one dashboard adds real work, and for many New York City congregations it is not optional.
- Integrations. Online giving, event registration, and livestream or recorded sermons each add setup.
One-time cost versus ongoing cost
Keep these two buckets separate in your head. The build is a one-time cost. Running the site is a small recurring one, and you cannot avoid it entirely:
- Domain name: about $12 to $20 a year. You should own this yourself.
- Hosting: from free up to about $25 a month, depending on the platform.
- Care and maintenance: optional. Backups, security, and small content changes, ideally something you can cancel anytime rather than a contract.
A quiet rule of thumb: if a quote bundles a big one-time build fee and a fat monthly fee with no clear ownership at the end, ask exactly what the monthly fee buys. Hosting and real support, fine. Permission to keep your own website, not fine.
What you should never pay for
- Unclear editing costs. Agree which updates your staff can make, what a care plan includes, and how extra work is quoted.
- A platform you cannot leave. If the site vanishes when you stop paying, you were renting, not buying.
- Vague monthly "SEO packages." The basics that actually help a church, correct service times, a Google Business Profile, and honest content, are a one-time setup, not a subscription.
- Pages you will never keep current. A blog nobody updates hurts more than it helps. Build only what you will maintain.
What I charge, and why it is fixed
I price church websites as a single project fee, not an hourly meter, because a church budget should be able to plan around a real number. It starts at $2,500 for a clear one-page presence and goes up from there for a full multi-page site your office runs itself. Care after launch is optional and cancellable. You can see the tiers and exactly what each includes on the pricing section of the home page.
If you are still weighing what you actually need before you think about cost, the checklist of what a church website should include is a good next read, or see how to build a church website step by step.
Common questions
- Is a free church website builder good enough?
- For a very small church with a volunteer who genuinely enjoys the upkeep, a free builder can carry you for a while. The catch is rarely the first month. It is the ad banners on some free tiers, the slow mobile load, the hard limits when you finally want a sermon archive or online giving, and the fact that the site tends to freeze the moment that one volunteer gets busy. Free is a fine place to start and a hard place to stay.
- Do I have to pay every month?
- You do not have to, but you will always have at least small running costs: a domain name is roughly $12 to $20 a year, and hosting is anywhere from free to about $25 a month depending on the platform. Ask which running costs are required and which support services are optional. Ongoing care (backups, security, small changes) is worth paying for, but it should be optional and cancellable, not a lock-in.
- How long does a church website take to build?
- A focused one-page site can be ready in one to two weeks once the content is in hand. A fuller multi-page site is usually three to five weeks. The slow part is almost never the building. It is gathering the content: service times, a paragraph about who you are, a few photos, and the giving link. Start collecting those early and everything else moves quickly.
- Who owns the website when it is finished?
- You should. Ask this plainly before you hire anyone. You want to own the domain name, the content, and the ability to move the site elsewhere if you ever part ways. Some cheap platforms rent you a site that disappears the day you stop paying. That is not ownership, and for a church it is a real risk.