VMware licensing costs in 2026, broken down. The SKU and the core count set most of the bill.

VMware cost in 2026 is the per core rate for your SKU multiplied by your licensed core count. Broadcom sets the rate, but you choose the SKU and the core count, and those two move the bill further.

What drives VMware licensing costs in 2026?

Your VMware bill is the per core rate for your SKU multiplied by your licensed core count, plus any add ons such as extra vSAN capacity. In our benchmarking, the SKU and the core count moved the total further than any discount on the rate did.

Most negotiation effort still goes into the rate, because the rate is the number printed on the quote. The SKU and the core count usually arrive already filled in by the account team, so the discount conversation starts from their base. The wider set of VMware guides sits in the VMware knowledge hub.

The inputs on every VMware quote

• The SKU. VMware Cloud Foundation, vSphere Foundation or vSphere Standard, each with its own per core rate.
• The licensed core count. Physical cores per CPU, with a 16 core minimum per CPU, summed across every host that has the software installed.
• Add ons. vSAN capacity above the included entitlement and advanced services, billed on top of the base SKU.
• The term. Annual or multi year. A longer term can hold the rate, provided the contract also limits what happens at the next renewal.

Which VMware SKU do you need: VCF, vSphere Foundation or vSphere Standard?

Choose the lowest SKU that covers the components you run today. Broadcom consolidated the VMware catalog into a short list, all licensed per core, so a bundle larger than your workload applies its higher rate to every core you license.

How to tell whether you need VCF

VCF earns its rate when you run NSX in production, provision through its automation layer, or hold more vSAN capacity than vSphere Foundation includes. A cluster that only virtualizes compute on external storage pays for unused components on every core.

• NSX. Does production traffic run on NSX segments? A lab install is not a reason to license VCF everywhere.
• Automation. Do teams provision through VCF Automation (formerly Aria Automation) today, or is it still a roadmap item?
• vSAN. How many TiB of vSAN capacity does each cluster hold, against 0.25 TiB per core under vSphere Foundation and 1 TiB per core under VCF?
• Monitoring. vSphere Foundation already includes VCF Operations, so monitoring alone does not justify the larger bundle.

The answer can differ by cluster, and a split between VCF and vSphere Foundation belongs in your quote request. The feature by feature comparison sits in VCF against vSphere Foundation.

What add ons do to the total

Extra vSAN capacity beyond the included entitlement, and advanced services, bill on top of the base SKU. On storage heavy environments they can rival the base subscription, so model them in the same sheet as the core count. Broadcom's counting script compares the vSAN capacity you run with the TiBs your cores include and reports any shortfall.

How does Broadcom count VMware cores, and what does the 16 core floor cost?

Every current SKU licenses physical cores with a minimum of 16 cores per CPU. Broadcom's VCF program terms require every core on a server where the software is installed to be licensed, including cores deactivated in the BIOS. A CPU with fewer than 16 cores is billed at 16 on every renewal until the hardware changes.

• Apply the floor per CPU. Count physical cores on each CPU and raise anything below 16 to 16. A host with two 12 core CPUs runs 24 cores and licenses 32.
• Consolidate onto dense hosts. Fewer, denser hosts mean fewer licensed cores. Buyers underuse this because the decision sits with infrastructure teams instead of procurement.
• Refresh low density hardware before the renewal. The business case is strongest while the subscription quote is still open. Small environments on 8 or 12 core CPUs feel the floor most in relative terms.

Owned cores and running cores

Licensing owned cores means paying for every core in the asset register. Licensing running cores means paying only for hosts that carry workload, after idle standby hosts, decommissioned kit and capacity held for growth are retired or consolidated. The gap between those two lists makes every other error more expensive.

Powering a host off does not take it out of scope while ESXi remains installed. Decide which hosts leave before the count is fixed, remove the software, and record the date and host names.

Why the floor penalizes older hardware

Buying more, smaller hosts was sound practice under socket based licensing and perpetual terms. Under a per core subscription with a floor, every CPU below 16 cores pays for capacity that does not exist. Two companies running identical workloads can therefore pay very differently on core density alone.

That makes consolidation a licensing decision as much as an infrastructure one. The counting rules are covered in more detail in VMware core licensing explained.

What does a VMware cost breakdown look like for a real host mix?

A hypothetical 40 host environment shows how far the SKU and core count move the bill before any discount. Actual rates vary by deal and partner, so the rates here are placeholders, not Broadcom prices: $260 per core per year for VCF and $200 for vSphere Foundation, a 30 percent bundle premium.

• 12 older hosts with two 14 core CPUs each: 336 physical cores, licensed as 384 because of the floor.
• 20 current hosts with two 24 core CPUs each: 960 cores, no floor effect.
• 8 standby hosts with two 16 core CPUs each and no production workload: 256 cores.

The last row is $160,000 a year below the first, about 38 percent, or $480,000 across a three year term. None of that came from the rate. The floor alone put 48 phantom cores on the older hosts, 14 percent above their physical count.

To run your own numbers, the per core subscription calculator gives a first pass, and the per core rates and discount bands are covered in VCF pricing 2026.

Where the example needs care

The hardware refresh on its own saves $16,640 a year at the VCF placeholder rate, or $49,920 over three years. That may not pay for five new servers, so the refresh makes most sense when the old hosts are due for replacement anyway.

vSAN changes the SKU comparison. At 1,280 cores, vSphere Foundation includes 320 TiB of vSAN and VCF includes 1,280 TiB. If the clusters hold 500 TiB, the vSphere Foundation option needs 180 TiB of add on capacity, and that price belongs in the same row before you compare.

Why did the first VMware renewal off perpetual cost so much more?

The purchase changed shape. A one time license plus annual maintenance became a recurring per core subscription, and in our benchmarking first renewals off perpetual multiplied annual cost 2 to 3 times. That is a structural change as well as a price rise.

Compare the quote with the right baseline

Compare total subscription cost with your prior license plus support spend. A comparison with list price flatters the quote and hides the structural jump.

Say you bought perpetual licenses for $450,000, ran them for nine years and paid $100,000 a year in support. Spread over those nine years, the licenses cost $50,000 a year, so your prior run rate was $150,000 a year. Measure the first subscription quote against that figure.

What happens if you keep running perpetual licenses

Perpetual licenses can continue to run, but new purchases and renewals are subscription only (the trade offs are in perpetual versus subscription). Broadcom's knowledge base article 429208 confirms hosts and vCenter keep operating after support expires, but patch downloads and support requests stop.

The same article warns against adding hosts or attempting major version upgrades during the gap, since both need active support for license conversion. Broadcom still needs the renewal to land, so bring a costed alternative: a migration, or a defined period on unsupported licenses with the security risk accepted. The pressure points are priced in the Broadcom VMware pillar.

What did VMware cost benchmarking show in 2024 and 2025?

Across roughly 30 to 40 Broadcom VMware environments we benchmarked in 2024 and 2025, landing in the wrong SKU was the most expensive single error. In 19 of the 30 plus we reviewed, the largest cost driver was a premium VCF bundle where vSphere Foundation covered the actual workload.

• The bundle premium. Companies that defaulted into VCF when vSphere Foundation covered their deployed components overpaid by 20 to 45 percent against the bundle the workload needed.
• The floor penalty. The 16 core per CPU minimum added 10 to 25 percent on low density hardware, permanently and on every renewal.

Why we reject the advice that the only choice left is the VCF term

The standard line from resellers is that the 2026 increase is unavoidable and the only remaining choice is which VCF term to sign. We disagree, because the benchmarking points elsewhere. A wrong bundle applies a premium rate to every licensed core, and a wrong core count inflates the number of cores that premium applies to.

A company that defaults into VCF and licenses its full owned inventory pays the higher rate on hardware that is idle, decommissioned or carrying nothing that needs the bundle. Neither error appears on the quote, because the quote is expressed as a rate, the one input the buyer cannot change.

The rate is set by Broadcom. Everything the rate multiplies is set by you.

The better course is to fix the SKU and the core count first, then benchmark the rate. A discount won on an inflated base leaves that base in place for the next renewal.

What will the Broadcom account team say about your VMware costs?

Expect the conversation to start from VCF and from the core count Broadcom already holds. These lines are common, with the reply we would give.

Which contract terms keep VMware costs from rising again?

Ask for terms that fix the rate, SKU mix and counting basis for the term and limit the next increase. Broadcom does not grant these by default, so put each in your first redline.

• Per core rate held for the term. Multi year terms can hold the rate where the environment is stable, paired with a cap so it does not reset in year three.
• A renewal cap. A stated maximum increase on the per core rate at the next renewal. See renewal cap benchmarks and price cap negotiation for wording and levels.
• The SKU mix by cluster. Name which clusters sit on VCF and which on vSphere Foundation.
• The agreed host list. Attach the host and CPU list behind the count, retired hosts marked, so any dispute starts from the same record.
• vSAN capacity priced per TiB. A per TiB rate for the term turns storage growth into a known cost.
• Reduction rights at renewal. The right to renew fewer cores, or move clusters to a lower SKU, without losing the discount level.

Broadcom's VCF program terms also require a compliance report 180 days after the license is registered and every 180 days after that. A late or missing report can degrade or block management features and suspend support, including access to updates, so give it a named owner.

How do you check your own VMware core count before the quote?

Run Broadcom's own counting script, then reconcile the output against your hardware records. Broadcom knowledge base article 313548 publishes a PowerCLI module, FoundationCoreAndTiBUsage.psm1, which reports licensed cores and vSAN TiBs under the current rules. It needs PowerCLI 13.3 or later and PowerShell 7.4.6 or later.

1. Export every host from each vCenter with its CPU count and cores per CPU. The vHost tab in RVTools gives the same data if you already use it.
2. Run the Broadcom script with all cores enabled in the BIOS, since the article warns that disabled cores make the results inaccurate.
3. Compare the host list with the asset register and flag hosts with no production workload.
4. For each cluster, record whether NSX, VCF Automation and vSAN are in use, and how many TiB vSAN holds.
5. Price the result under each SKU in one sheet, including add ons, before the account team sends its own count.

Check test labs and disaster recovery sites separately, since they often sit in a different vCenter from production.

What to do next

1. 12 months before renewal. List every VMware host by CPU and physical cores per CPU, then apply the 16 core per CPU floor to compute the licensed core count.
2. 9 to 12 months out. Separate owned cores from running cores, retire or consolidate hosts that carry no workload, and decide on refreshing CPUs below 16 cores.
3. 6 months out. Map which VCF components you actually deploy, cluster by cluster, and choose the lowest SKU that covers the real workload.
4. 4 to 5 months out. Model vSAN overage and advanced services in the same sheet as the base SKU, then request a quote on your own host list and SKU split.
5. 3 months out. Benchmark the renewal and prepare a costed migration option you would act on. Our VMware exit plan guide sets out how to build one.
6. 1 month out. Put the rate hold, renewal cap, host list and SKU mix into the order form before you sign. The Broadcom practice runs the core and SKU work with you.

Frequently asked questions