Kinsta Bandwidth vs Visits: The Pricing Model That Meters Everything

The three-meter system

Before October 2025, Kinsta billed entirely by visits. Every plan had a visit cap. Go over, pay $0.50 per 1,000 extra visits. Bot traffic, crawlers, scraped pages: all counted. No escape hatch.

The bandwidth option changed the billing model but not the monitoring architecture. After switching to bandwidth-based billing:

• Server bandwidth becomes your primary meter. Overage: $0.50 per extra GB.
• Visits are still tracked in MyKinsta Analytics (Company Settings > Analytics > Resources) but do not trigger overage charges.
• CDN bandwidth remains a separate meter with its own overage ($0.05 per extra GB), regardless of which billing model you selected.

On visit-based billing, the arrangement mirrors itself: visits trigger overages, server bandwidth is tracked but not billed, and CDN bandwidth is still independent.

The practical effect: you see two of the three metrics climbing in your dashboard without being billed for them, but knowing they exist. If you picked bandwidth and notice your visits are running high, the question becomes whether you chose the right model. Switch the billing, switch the worry. There is no version of Kinsta pricing where you stop watching a number climb. Kinsta designed a system where your unchosen metric is always visible, always climbing, and always suggesting you might have picked wrong.

A detail that matters: server bandwidth only counts data sent by WordPress directly from the origin server. HTML pages, CSS, JavaScript, and media served from the origin. It does not include data served from Cloudflare's CDN or Edge Cache. So your server bandwidth number is a narrow slice of total data transfer, not the full picture.

Plan pricing and what each tier includes

Each visit-based plan has a bandwidth-based equivalent at the same price. You choose which meter to use, not which plan to buy. Current pricing (monthly rates):

Storage on every single-site plan: 10 GB. On a $290/month plan, you get the same 10 GB disk space as the $35 plan. Extra storage costs $2/GB/month, prorated daily. For a WooCommerce store with product images, 10 GB fills fast. The add-on costs stack up from there: Redis at $100/month, extra PHP memory at $10 per 500 MB, additional backups at $20/month for hourly or $50 for every-six-hours.

How overages work

Kinsta does not throttle your site when you exceed limits. Traffic keeps flowing. The bill keeps growing. Overage rates:

The extreme overage clause: if your overage charges equal or exceed your plan cost or $500 (whichever is less), Kinsta can demand immediate payment, force a plan upgrade, or restrict site access. On the $35 entry plan, that threshold is $35 in overage. At $0.50 per 1,000 visits, that is 70,000 extra visits beyond your 35,000 cap. A moderately successful blog post going viral can trigger that in a weekend.

Kinsta sends email alerts at 80% usage, 100%, and 10% over the limit. No spending cap exists. You cannot set a maximum overage amount. The bill is whatever the traffic generates.

Contrast with how other hosts handle traffic spikes:

• WP Engine: Charges $2 per 1,000 extra visitors (4x Kinsta's rate). But only one meter to worry about.
• Cloudways: No visit counting at all. Bandwidth overage on Vultr is $0.01/GB in North America and Western Europe, $0.025/GB in Singapore and Tokyo. One-fiftieth of Kinsta's bandwidth overage rate.
• Pressable: Charges $1.20 per 1,000 extra visits. More expensive than Kinsta per visit but with explicit warnings against WooCommerce on staging (a separate problem).

The bot traffic problem

This is the reason Kinsta added bandwidth-based billing in the first place. AI crawlers exploded in 2025. Kinsta's own analysis of their network data: 1 in 31 web visits is now an AI bot (up from 1 in 200 at the start of 2025). GPTBot traffic grew 305% between May 2024 and May 2025. Akamai reported a 300% surge in AI bot traffic over the same period.

One documented case: a site owner at nimble.help reported that 70% of their billed visits were bot traffic. Amazon AWS IP addresses alone made up over 30% of daily visits. The site owner ultimately migrated away from Kinsta because the bot mitigation tools were not sufficient to keep their visit count under control.

Kinsta's response, announced November 4, 2025: customers on bandwidth-based billing will not be charged for bandwidth consumed by unwanted bot and scraper traffic. They launched a Bot Protection Tool in MyKinsta and partnered with Cloudflare for filtering. CTO Daniel Pataki acknowledged that bots have altered typical bandwidth-to-visit ratios, making traditional billing unfair.

The catch: bot filtering works on bandwidth-based plans. If you stay on visit-based billing, bots that spoof user agents are still counted as visits. Kinsta's visit counting documentation is explicit: visits are counted server-side. The same person on two networks counts as two visits. CDN and Edge Cache requests count. The structural discrepancy with Google Analytics (which relies on JavaScript execution) means Kinsta will always report higher visitor numbers than your analytics dashboard.

Kinsta vs WP Engine vs Cloudways: meters compared

The structural difference is how many things each host measures and bills.

At equivalent traffic levels, what each host costs:

Kinsta and WP Engine are roughly comparable in the 100-250K range, with WP Engine slightly cheaper at lower tiers and slightly more expensive at higher ones. Cloudways is 70-80% cheaper across the board because it has no visit counting, no per-site pricing, and bandwidth overage rates that are fifty times lower than Kinsta's.

The trade-off: Kinsta's infrastructure is faster out of the box (Google Cloud C2 machines, Cloudflare Enterprise integration on every plan). Cloudways requires you to pick your own infrastructure tier and manage more configuration. WP Engine sits in between. You pay Kinsta's premium for the performance and the managed experience, not for the billing model.

FAQ