Kinsta Pricing in 2026: Visit vs Bandwidth Plans, Limits, and Overages

The short answer: Kinsta Managed WordPress Hosting starts at $35 per month for one site, or a displayed $30 monthly equivalent with annual billing. At each price tier, you choose either a monthly-visit allowance or a server-bandwidth allowance. The visit option is easier to budget when you understand your Kinsta-style visit count. The bandwidth option can be better for a lightweight or heavily cached site with many visitors, because traffic served from a CDN or edge cache does not count as server bandwidth.

This guide covers Kinsta’s English-language Managed WordPress Hosting prices in USD. We reviewed public pricing and documentation but did not open a paid account, migrate a site, measure production performance, or test support. Prices, limits, and policies were checked on August 24, 2026 and can change.

Kinsta Pricing at a Glance

Kinsta separates its public WordPress plans into single-site and multi-site tiers. Most tiers have two versions at the same subscription price:

• A visits-based plan, limited by Kinsta’s monthly visit count
• A bandwidth-based plan, limited by data sent directly from Kinsta’s origin server

You select one pricing model. A plan does not apply both allowances at once. Storage, CDN bandwidth, site count, and other plan limits still apply under either model.

Choose either the visit allowance or the server-bandwidth allowance shown for a price tier. The two allowances do not apply together. Annual prices are displayed monthly equivalents paid on an annual billing cycle.

The entry single-site pair—Single 20GB or Single 35k—costs $35 with monthly billing. Its annual option is displayed as a $30 monthly equivalent. Both versions include one WordPress site, 10GB of storage, 125GB of CDN bandwidth, and 14 days of backup retention.

The entry multi-site plan, WP 2, costs $70 monthly or a displayed $59 monthly equivalent with annual billing. It includes two WordPress sites, 20GB of storage, 250GB of CDN bandwidth, and 14 days of backup retention.

Annual figures are monthly equivalents for an upfront annual commitment, not month-to-month prices. Taxes and paid add-ons can increase the total.

Visit-Based vs Bandwidth-Based Pricing

The two pricing models answer different questions.

Visit-based pricing measures daily unique IP addresses

Kinsta calculates monthly visits by adding the unique IP addresses seen during each 24-hour period. The allowance is shared by all live WordPress sites in the plan.

One person viewing multiple pages from the same IP address on the same day generally counts as one visit. The same person can count again on another day, and using a different network can create another visit. Visits served through Kinsta’s edge cache or CDN are still included in the visit count.

This number will not necessarily match Google Analytics. Client-side analytics can miss people who block tracking, while Kinsta measures requests at its infrastructure. Kinsta filters most recognized bots, but some automated traffic can still consume resources and be counted.

Choose a visits-based plan when:

• You can estimate traffic using server-side data or Kinsta’s counting method
• Page weight and download size vary, but visitor volume is relatively predictable
• A simple visitor allowance is easier for your team or clients to understand
• You prefer overage units of 1,000 visits instead of gigabytes

Do not select a plan from the monthly users or sessions shown in a marketing analytics dashboard alone. Compare the definition first and leave room for campaigns, bot traffic, and seasonal peaks.

Bandwidth-based pricing measures origin traffic

Server bandwidth is the data Kinsta’s origin server sends in response to requests, including HTML, images, scripts, stylesheets, API responses, and downloads. Data served by a CDN or edge cache is excluded from this measurement.

This can make bandwidth pricing attractive for a site with many visitors but efficient pages and a high cache-hit rate. It can be harder to predict for uncached applications, large file delivery, APIs, membership sites, or pages that frequently bypass cache.

Choose a bandwidth-based plan when:

• You can measure or estimate origin traffic separately from total CDN traffic
• Most public traffic is cacheable
• Visitor counts are high relative to the amount of origin data transferred
• Your team already monitors bandwidth and can respond to usage alerts

The important input is origin-server bandwidth, not the total transfer number from an unrelated CDN or analytics product.

A Practical Way to Choose Between the Two Models

Start with real workload data rather than the plan name.

1. Record daily visits from your current server-side analytics for at least one normal month.
2. Identify peak months caused by launches, advertising, press coverage, or seasonality.
3. Measure the amount of data delivered by the origin after subtracting CDN or edge-cache traffic where possible.
4. Estimate how much uncached traffic comes from logged-in users, carts, dashboards, APIs, and downloads.
5. Compare the visit and bandwidth tier at the same price.
6. Add headroom and calculate the cost of one realistic overage month.

For example, the $35 single-site tier offers either 35,000 visits or 20GB of server bandwidth. A site with 60,000 mostly cached visits and 12GB of origin traffic may fit the bandwidth version while exceeding the visit version. A site with 25,000 visits and 28GB of uncached origin traffic may fit the visit version while exceeding the bandwidth version.

Those examples illustrate the calculation only. They are not performance estimates or guarantees, and both sites must still fit the storage and CDN limits.

Kinsta Overage Fees

Kinsta keeps a site online when it passes a normal plan allowance, then bills overage usage. The current public rates are:

Plan-limit alerts are enabled by default. Kinsta says it sends alerts at 80% and 100% of plan usage; visit-based plans also receive an alert after exceeding the allowance by 10%.

Upgrading does not erase overages already incurred. The new plan applies from the time of the change, while earlier overages remain billable.

Overage examples

If a 35,000-visit plan records 50,000 visits, the 15,000 excess visits cost:

15 × $0.50 = $7.50

If a 20GB bandwidth plan uses 28GB of server bandwidth, the 8GB excess costs:

8 × $0.50 = $4.00

If CDN delivery exceeds its allowance by 100GB, the CDN overage costs:

100 × $0.05 = $5.00

These calculations exclude the subscription, disk overages, taxes, and add-ons. An unusually large overage can trigger earlier payment or a required plan change under Kinsta’s policy, so overages should be a safety margin rather than a long-term capacity strategy.

What Is Included in the Plan Price?

The current public plan table lists the following across the standard WordPress tiers:

• Unlimited free migrations handled through Kinsta’s migration workflow
• A staging environment for each WordPress installation
• Automatic, manual, and system-generated backups
• Kinsta CDN powered by Cloudflare
• Free SSL certificates with wildcard support
• A managed web application firewall and DDoS protection
• Malware-removal assistance
• Built-in application performance monitoring
• 24/7 chat access to support
• Unlimited account users with access controls

Backup retention varies by plan. Lower tiers generally retain backups for 14 days, while higher tiers extend this to 20 or 30 days. Optional hourly or six-hour backup schedules, external backups, extra disk space, premium staging environments, Redis, and other specialized resources can cost extra.

Included features do not prove that a plan has enough compute capacity for every workload. Dynamic ecommerce, membership, and learning sites can require more PHP resources even when their visit, storage, and bandwidth numbers fit.

Which Single-Site Plan Should You Choose?

Choose the $35 tier for a small production site

Single 20GB or Single 35k is the starting point for one brochure site, portfolio, publication, or modest business site. It includes 10GB of storage and 125GB of CDN bandwidth.

It is less suitable for a media-heavy library, large WooCommerce catalog, membership site, or workload with frequent uncached requests. A plan can fit its headline visit allowance and still be constrained by storage or compute requirements.

Move to $50 or $90 when traffic—not site count—is growing

The $50 tier raises the choice to 65,000 visits or 40GB of server bandwidth. The $90 tier raises it to 125,000 visits or 65GB of server bandwidth. Storage remains 10GB on both tiers, so paying more for traffic capacity does not automatically solve a storage problem.

Use higher single-site tiers for a genuinely high-traffic workload

The $170, $290, and $375 tiers provide much larger traffic allowances but remain single-site plans. They make sense when one important site needs capacity without paying for many WordPress installations.

Before choosing one, ask Kinsta to confirm the PHP resources, backup retention, migration scope, and expected behavior for your workload. Public traffic and storage limits do not describe every performance boundary.

Which Multi-Site Plan Should You Choose?

WP 2 is the entry point for two production sites

WP 2 includes two WordPress installations and shared plan resources. The sites share 70,000 visits or 40GB of server bandwidth, 20GB of storage, and 250GB of CDN bandwidth.

The word “shared” matters. Two sites do not each receive the full allowance.

WP 5 fits a small client or company portfolio

WP 5 costs $115 monthly or a displayed $96 monthly equivalent with annual billing. It includes five sites, 30GB of storage, and either 125,000 visits or 65GB of server bandwidth.

It can fit a small agency only when the combined workload stays within the shared limits. One busy client site can consume a disproportionate part of the account.

WP 10 and above require portfolio-level capacity planning

WP 10, WP 20, and WP 40 increase site count, storage, traffic allowances, and CDN bandwidth. These plans are easier to justify when centralized migrations, staging, access management, and support replace meaningful internal operating work.

For client hosting, decide how usage alerts, overages, backups, incident communication, and ownership transfers will be handled before placing many unrelated businesses in one shared plan.

First Month Free and the Money-Back Guarantee

Kinsta currently lists the first month free on the entry Single 20GB, Single 35k, and WP 2 options. The pricing page shows $0 due for the first month and the normal subscription price afterward.

Kinsta also documents a 30-day money-back guarantee for first-time Managed WordPress Hosting customers. For entry plans with a free first month, the guarantee begins from the renewal date after the free period.

Important exclusions include:

• Overages
• Dedicated-server fees
• One-time fees
• Other charges incurred during the guarantee period

Do not treat the offer as a completely cost-free production load test. Confirm the current checkout total and guarantee terms before migrating, and monitor usage during the free period.

Costs Beyond the Subscription

Budget for more than the headline monthly price:

• Usage overages
• Applicable taxes
• Additional storage
• Additional WordPress sites
• Premium staging environments
• More frequent or external backups
• Redis or other performance add-ons
• Dedicated resources for demanding sites
• Internal migration testing and DNS cutover work

Kinsta lists an additional WordPress-site add-on at $30 per month. The add-on increases the site count but does not add visits, server bandwidth, storage, or CDN capacity; those resources remain shared by the plan.

Who Kinsta Is Best For

Kinsta is a strong candidate when a business values managed migrations, staging, backups, security controls, access management, and 24/7 support more than the lowest possible hosting price.

It can fit:

• Businesses running an important WordPress site without a dedicated infrastructure team
• Agencies that need consistent staging, handoff, and account-access workflows
• Publishers that can estimate visits or origin bandwidth accurately
• Teams willing to monitor plan usage and pay for managed operations

Kinsta may be a poor fit when:

• The main requirement is the cheapest place to host a small site
• Storage needs are high relative to traffic
• Traffic, bot activity, or origin bandwidth is difficult to forecast
• A workload needs dedicated compute but the budget only covers an entry plan
• You need reseller billing bundled into the hosting product
• You expect a managed host to eliminate application-level performance work

Final Recommendation

For one ordinary WordPress site, start the comparison with Single 20GB versus Single 35k. Choose the allowance you can measure more reliably, then verify that 10GB of storage, 125GB of CDN bandwidth, 14-day backup retention, and the available compute resources fit the site.

Use WP 2 or WP 5 when multiple production sites make centralized management worthwhile, not simply because the per-site arithmetic looks lower. All headline resources are shared, so size the plan for the busiest combined month.

Avoid annual billing until you have measured real usage on Kinsta and confirmed that visits, origin bandwidth, storage, CDN traffic, and dynamic workload requirements are stable. The annual discount is less valuable than choosing the wrong pricing model or resource tier.

If you are also considering another premium managed host, read our Kinsta vs WP Engine comparison.

Frequently Asked Questions

How much does Kinsta cost per month?

Kinsta Managed WordPress Hosting starts at $35 per month for one site. The annual option is displayed as a $30 monthly equivalent. The entry single-site plans currently include the first month free.

Does Kinsta charge by visits or bandwidth?

You can choose either model on current Managed WordPress Hosting tiers. Visits-based plans use Kinsta’s monthly visit count. Bandwidth-based plans measure data delivered by the origin server and exclude traffic served from a CDN or edge cache.

What happens if I exceed a Kinsta limit?

Kinsta normally keeps the site running and charges overages. Current public rates are $0.50 per 1,000 visits, $0.50 per GB of server bandwidth, $0.05 per GB of CDN bandwidth, and $2 per GB per month for disk space calculated daily.

Does every Kinsta site get its own allowance?

No. Visits or server bandwidth, storage, and CDN bandwidth are shared across all WordPress sites in a plan.

Is Kinsta’s first month completely free?

The subscription price is currently $0 for the first month on eligible entry plans, but overages and excluded fees can still apply. Check the checkout total and current money-back terms before starting a production migration.