Virginia's budget now turns on data centers: a tax-break fight and a new impact-fee proposal head into a June 30 cliff
Virginia's state budget — normally a fight about schools and Medicaid — has become, this month, a fight about data centers. Two threads are converging on the same deadline:
What changed
Virginia's state budget — normally a fight about schools and Medicaid — has become, this month, a fight about data centers. Two threads are converging on the same deadline:
- A data-center tax-break dispute. Changes to Virginia's data-center sales-and-use tax exemption are, per WYDaily (pub. 2026-06-14), "still holding up" the budget. By June 17, WJLA/WSET were reporting that "Richmond budget talks ramp up ahead of the June 30 deadline as the House cancels session" with the data-center tax-break dispute named in the headline, alongside the phrase "Virginia government shutdown."
- A new statewide data-center impact fee. 29News (pub. 2026-06-17) reports a Virginia Senate impact-fee proposal for data centers that "meets pushback" even as "budget negotiations move forward."
The clock is explicit: WDBJ7 (pub. 2026-06-17) headlined that "Virginia lawmakers have 13 days to pass a budget or face [the state's] first government shutdown." On June 16, the House and Senate released competing budgets (WHRO, WTOP, WYDaily), and data-center revenue treatment is one of the lines on which they "align and diverge."
Sources (all in-repo, SitePath's news index, source_quality_score 0.85):
- WJLA / WSET —
https://wjla.com/news/local/richmond-budget-talks-ramp-up-ahead-of-june-30-deadline-as-house-cancels-session-data-center-tax-break-dispute-virginia-government-shutdown-june-2026 - 29News —
https://www.29news.com/2026/06/17/va-senate-impact-fee-proposal-data-centers-meets-pushback-budget-negotiations-move-forward/ - WYDaily —
https://wydaily.com/latest/2026/06/14/data-center-tax-exemption-changes-still-holding-up-virginia-budget/ - WDBJ7 —
https://www.wdbj7.com/2026/06/17/virginia-lawmakers-have-13-days-pass-budget-or-face-first-government-shutdown/ - WHRO —
https://www.whro.org/virginia-government/2026-06-16/the-house-and-senate-both-released-new-budgets-heres-how-they-align-and-diverge
Why it matters for siting
Virginia is the center of gravity for U.S. data centers — Loudoun and Prince William alone anchor the world's densest cluster. Two of the biggest levers that decide where the next gigawatt of compute lands are exactly what's now on the table in Richmond:
- The sales-and-use tax exemption is one of the main reasons hyperscalers chose Virginia over neighboring PJM states. Narrowing or conditioning it — the "tax-break dispute" — changes the after-tax math for every prospective site and could push marginal projects toward Maryland, Pennsylvania, West Virginia, or the Carolinas. SitePath already logs (in SitePath's change feed) the FERC directive ordering PJM to write co-location rules for AI data centers paired with generation; a Virginia tax change would interact directly with where that co-located solar-plus-storage capacity gets built.
- A statewide impact fee would be a new, uniform cost layer on top of the patchwork of county conditions SitePath tracks. If it passes, it reshapes the county-by-county competitive map overnight — and gives localities a revenue tool that may cool the local backlash now visible across the state.
That backlash is real and in the same news window: a Prince William "Digital Gateway" town hall drew community debate over the rezoning (WJLA, 2026-06-16); Fauquier County's "Gigaland" developers are offering "millions of dollars to local nonprofits" ahead of approval (FauquierNow / InsideNoVa, 2026-06-15); Louisa County is wrestling publicly with data-center water discharge (NVDaily, 2026-06-15); and Halifax County approved its own budget with "questions remain[ing] over data centers" (Roanoke Rapids Daily Herald, 2026-06-16). The state-level fight and the local-level friction are the same story at two altitudes.
The wider signal: a national moratorium wave
Virginia is not alone. In the same 72-hour window, SitePath's news feed logged a cluster of new local data-center pauses well outside the Mid-Atlantic:
- Gage County, NE — Planning & Zoning approved an 18-month moratorium (Nebraska Public Media / 1011Now, 2026-06-17).
- Versailles, KY (Woodford Co.) — City Council enacted a moratorium through 2026; other KY counties "hitting pause" (LEX18, Highland County Press, 2026-06-18).
- Superior & Winnebago, WI — Superior joins a "growing number" of WI communities passing moratoria; Winnebago County to pursue a 12-month pause (WPR, 943JackFM, 2026-06-17).
- Box Elder, UT (UPR) and Desert Hot Springs, CA (KESQ) — both hit pause (2026-06-17).
- Boulder County, CO — commissioners declared a moratorium (KGNU, 2026-06-16).
Counter-example, same window: Uinta County, WY unanimously approved a conditional-use permit for Prometheus Hyperscale (PR Newswire, 2026-06-17) — the brakes are not universal.
Important caveat: none of these moratoria has yet been ingested into SitePath's verified dataset. As of the 2026-06-20 sync, SitePath's data-center dataset still reports 22 active moratoria — unchanged. These are news-feed signals, not yet primary-source-verified records. The verified count understates the field and should be reconciled.
Bottom line
For the first time in this dataset's recent history, Virginia's entire state budget is hostage to data-center policy — both a tax-exemption fight and a brand-new impact-fee proposal — with a hard June 30 deadline and a credible shutdown threat. Whatever Richmond decides in the next ~10 days will reset the siting economics for the country's largest data-center market and ripple across PJM. It lands the same week VA's HB 711 / SB 347 solar/BESS local-ban preemption takes effect (2026-07-01), making the first days of July a genuine inflection point for Mid-Atlantic energy siting. SitePath should verify the budget language the moment it's public and promote both the Virginia development and the national moratorium wave into the curated regulatory feeds.
Published from the SitePath editorial desk on June 21, 2026. Claims are traced to primary documents and to records already in the SitePath dataset; source links appear inline. Material the source review could not confirm has been withheld from this page rather than published with a caveat — see methodology for how SitePath sources and scores what it publishes.