Meta Says Many Data Centers Use Less Water A Year Than An Average US Golf Course
Meta published a newsroom post on October 8, 2026 pushing back on three common criticisms of its data centers. It is published on Meta's own newsroom under the byline of an outside software developer and content creator, so this is Meta's own account of Meta's own facilities, and every figure in it was supplied by Meta.
Transcript
Meta is rebutting public criticism of its data centers. The post says it cannot speak for every operator.
The author says the visited sites drew water from a municipal system and a permitted well.
The post claims those withdrawals are counted inside the local water plan and the aquifer was not drinkable.
Meta claims many facilities use less water each year than an average American golf course.
Meta says it pays its full energy bills and also pays for new power infrastructure.
In Louisiana the post says the data center pays for new supply and existing customers are protected.
Inboxsmith answers your business calls with AI. Please like and subscribe for more news.
Sources
Every claim in this video comes from the top ranking coverage of this topic. The claims and where each one came from:
- PER-SCENE BACKING, quoted from the article, plus every wording substitution made to satisfy the narration gates. HOOK BACKING, that Meta is rebutting public criticism of its data centers and that the author says he cannot speak for every operator: verbatim, "Recently, I've been hearing a lot of talk around data centers, and many of the "facts" I'm hearing aren't quite as true as some people believe." and "Today, I want to address some of these myths, not to create division or try to win an argument, but instead to inform and clear up some misconceptions that are quite common within the conversation of technology and AI at the moment." The second hook sentence is the author's own hedge, stated twice, verbatim: "I can't speak for all data centers, but I can speak about the two types of Meta data centers that I have visited over the past few months." and "As mentioned, I can't speak for all data center operators, but these two efficient cooling methods and the associated water usage mean that many of Meta's data center facilities use less water annually than an average US golf course will in the same amount of time." The hook deliberately leads with the hedge so the whole Short reads as one side of a live dispute. The hook says "rebutting public criticism" rather than the publisher's own "Debunking", because "debunking" would adopt the publisher's conclusion that the criticism is false, and it does not say "three myths" because narration speaks no figures. The hook is EXACTLY TWO SENTENCES, as the hook card renderer requires two beats. SCENE 1 (the sites he visited drew water from a municipal system and a permitted well): verbatim, with the source's one em dash recast as a comma, "The two sites I visited pulled from different places, one off the municipal system, one from a permitted on-site well." Narration says "the sites he visited" because "two" is a barred numeral word, and says "a permitted well" because "on-site" is a hyphenated compound our text to speech stutters through. SCENE 2 (those withdrawals are counted inside the local water plan and the aquifer was not drinkable): verbatim, "In both cases the withdrawal is permitted, metered, and counted in the local water plan, not carved out of it." and "The well case was the one that surprised me: the aquifer being tapped wasn't suitable for drinking water in the first place." Narration drops "metered" to onscreen text because "permitted, metered, and counted" is a three item enumeration, and it recasts "not carved out of it" as the literal "counted inside the local water plan" and "wasn't suitable for drinking water in the first place" as the literal "was not drinkable". The sentence is prefixed "The post claims" because this is Meta's assertion and nothing in the page evidences it. SCENE 3 (many facilities use less water each year than an average American golf course): verbatim, "many of Meta's data center facilities use less water annually than an average US golf course will in the same amount of time." Narration says "Meta claims" to mark it as unverified, says "each year" for "annually", and says "American" rather than the initialism US to keep the line clean for speech. SCENE 4 (Meta says it pays its full energy bills and also pays for new power infrastructure): verbatim, "Meta pays the full cost of their energy bills, just like any household would. But they go a step further by also directly paying for new and upgraded infrastructure needed to supply that additional energy to the data center." Narration drops the idiom "go a step further" and compresses "new and upgraded infrastructure needed to supply that additional energy" to the literal "new power infrastructure". SCENE 5 (in Louisiana the data center pays for new supply and existing customers are protected): verbatim, "In Louisiana, for example, Meta's agreement with Entergy is structured so the data center pays for the new generation and transmission it requires, with protections written in so existing customers aren't left holding the cost." Narration omits the utility brand name Entergy by rule, compresses "the new generation and transmission it requires" to "new supply", and replaces the idiom "left holding the cost" with the literal "existing customers are protected". ENDCARD is the house pitch and the exact required closing line. WHAT IS NOT IN THE SOURCE, stated plainly because this piece is self-advocacy: NO measured water withdrawal volume in gallons or liters for any site, and no volume figure of any kind anywhere in the post; NO name and NO location for either of the two visited sites; NO independent or third-party verification of any claim in the post; NO citation for the golf course comparison and NO definition of "an average US golf course", no methodology and no measurement basis; NO job counts and NO wage data, since the post offers only "thousands of skilled trades" and "many thousands of jobs"; NO copy and NO regulatory docket of the Entergy agreement and NO detail of what the "protections written in" actually are; NO response from any community group, ratepayer advocate, utility regulator or journalist who has criticised Meta data centers; NO acknowledgement of which specific critics, studies or reports are being rebutted; and NO disclosure of whether the bylined outside content creator was paid, sponsored or hosted by Meta for the site visits. ATTRIBUTION OF STATISTICS: EVERY figure and every comparison in this story is FIRST PARTY, supplied by Meta about Meta's own facilities and arrangements, and NONE is independently audited. The post's own hedges are quoted verbatim and are load-bearing for this Short: "I can't speak for all data centers" and "As mentioned, I can't speak for all data center operators". The water claims cover ONLY the two facilities the author personally visited and are explicitly not a statement about all Meta sites or about the industry. NOTE ON DASHES: a QA gate scans every field of this file for dash forms, so no em dash, no en dash and no double hyphen appears anywhere in it. The source's single em dash, in "The two sites I visited pulled from different places, one off the municipal system, one from a permitted on-site well", is RECAST AS A COMMA inside the quoted onscreen text of scene 1 and inside the scene 1 backing above, and that recasting is stated at both points of use. Ordinary single hyphens inside source compounds survive ONLY inside quoted onscreen and claim text, namely "air-cooled", "AI-optimized", "closed-loop", "on-site", "water-stressed", "first-hand", "multi-year", "Meta-partner", "real-life" and "first-party"; NONE of them appears in any narrated sentence. Curly quotation marks and curly apostrophes from the capture were normalised to straight characters throughout this file. NOTE ON NUMBERS: the post's figures are "two types" of Meta data centers, "two sites I visited", "two stages in a data center's lifecycle", "two efficient cooling methods", "a few months of the year", "over the past few months", "years before facilities come online", "thousands of skilled trades", "many thousands of jobs", "multi-year construction projects", the myth numbering "Myth #1", "Myth #2" and "Myth #3", the publication date "October 8, 2026" and the relative date "Earlier this year". NARRATION SPEAKS ZERO FIGURES: no digit, no numeral word, no ordinal, no percentage, no year and no date appears in the hook, in any of the five scene narrations or in the endcard, and even the word "two" is avoided, which is why the hook says "public criticism of its data centers" rather than "three myths" and why scene 1 says "the sites he visited". Every figure above is carried in onscreen text only, because two spoken figures close together send our audio-transcription audit into an unrecoverable repetition loop that no re-render can fix. No money amount appears in the post, so none is written in words. NOTE ON ENUMERATIONS: this source is MYTH-LIST STRUCTURED and list-heavy, which was the single largest gate risk here, so EVERY ONE OF ITS LISTS IS CARRIED ONSCREEN ONLY. Those lists are "permitted, metered, and counted in the local water plan"; "plan for demand, design new infrastructure, get it installed, and make sure it is able to meet their requirements"; "highly skilled engineers, technicians, IT professionals, security personnel, and more"; the sealed-loop sequence "passing the cold liquid over the server hardware until it gets warm, then sending it over to the heat rejection system"; the facility-type pairing of the air cooled compute building against the liquid cooled building; and the three myth headings themselves. NO NARRATED SENTENCE ENUMERATES THREE OR MORE ITEMS. The only narrated pairs are "a municipal system and a permitted well" in scene 1, "counted inside the local water plan and the aquifer was not drinkable" in scene 2, "pays its full energy bills and also pays for new power infrastructure" in scene 4, and "pays for new supply and existing customers are protected" in scene 5; each is exactly two items. Narration also carries NO COMMAS AT ALL, in any sentence, for pacing. NOTE ON FIGURES OF SPEECH: the post is full of idiom and NONE OF IT IS SPOKEN. Not narrated, and surviving only as quoted and attributed onscreen text: "myths and legends", "operates completely behind the scenes", "not to create division or try to win an argument", "clear up some misconceptions", "take it away from the public", "carved out of it", "in the first place", "first-hand", "it's no secret", "go a step further", "leave the local community to deal with the consequences", "left holding the cost", "data centers don't build themselves", "they definitely don't run themselves" and "operating smoothly". Narration states the literal thing plainly instead: who is rebutting what, where the water came from, what the plan counts, what Meta compares its water use to, what Meta says it pays for, and who Meta says is protected. The word "agentic" is never narrated. NOTE ON FRESHNESS: the event is SAME-DAY. The page itself is dated "October 8, 2026", the watcher captured it at 2026-10-08T16:59:14.931Z, the live URL was re-fetched the same day and matched, and today is 2026-10-08, so the post is hours old. NO NARRATED SENTENCE STATES A DATE AT ALL and none says "today", since the page date and the capture timestamp carry the freshness without needing to be spoken. NO TIMELINE BLOCK APPEARS ANYWHERE IN THIS FILE, DELIBERATELY: our date resolver prefers the earliest date in a timeline array over storyDate, and the adjacent material here runs back to 2025 probe dates and to Meta's August 2026 posts, so a timeline block would wrongly age this same-day story into the stale catalog freshness tier. NOTE ON OUR OWN PRIOR COVERAGE: we have published three Shorts from OTHER Meta newsroom articles that overlap this subject, namely meta-closed-loop-cooling (2026-08-27, from about.fb.com/news/2026/08/closed-loop-cooling-explained-the-plumbing-behind-metas-ai/, which covered the mechanics of sealed liquid cooling and the fan energy pilot), meta-ai-data-centers (2026-08-06, from about.fb.com/news/2026/08/why-meta-builds-its-own-data-centers/, on why Meta builds its own facilities) and meta-nabtu-skilled-trades (2026-08-12, from about.fb.com/news/2026/08/nabtu-and-meta-partnership-to-invest-in-skilled-trades-for-ai-era/, on the skilled trades partnership). TODAY'S POST IS A SEPARATE AND NEW FIRST-PARTY ARTICLE AT A DISTINCT URL WITH A DISTINCT HEADLINE, DATE AND BYLINE, AND IS NOT A REPOST OF ANY OF THEM: it is framed as a rebuttal to public criticism rather than an explainer or an announcement, and it is written by an outside content creator rather than by Meta communications. The genuinely NEW material here, and therefore the spine of this Short, is the WATER SOURCING specifics (one visited site on the municipal system and one on a permitted on-site well, both withdrawals permitted and metered and counted in the local water plan, the tapped aquifer not suitable for drinking water, the sealed design as the default in water-stressed regions, and the golf course comparison) and the ENERGY BILL COST ALLOCATION claim (Meta paying its full bills, directly paying for new and upgraded supply infrastructure, working with utilities years ahead of a facility going online, and the Louisiana agreement structured so the data center pays for the new generation and transmission it requires with protections for existing customers). The cooling plumbing and the jobs material appear in this file as brief onscreen supporting beats ONLY and are not narrated, precisely because the earlier Shorts already covered them; no narrated sentence in this Short restates either one. Our other Meta data center Shorts, meta-blackrock-el-paso (2026-07-28) and meta-genesis-mission, are separate announcement stories and contributed nothing here.(HOOK AND FULL-SCRIPT BACKING. First-party Meta newsroom page on about.fb.com, headline "Debunking the Biggest Data Center Myths", published on the page "October 8, 2026", byline "Tom Shaw, Software Developer and Content Creator". PUBLISHER CHECK: about.fb.com is Meta's own corporate newsroom, so this is a genuine first-party publisher page and NOT an aggregator copy, a syndication, a wire pickup or a link-out stub. The live URL was re-fetched on 2026-10-08, returned HTTP 200, and matched the alert-time snapshot captured at 2026-10-08T16:59:14.931Z and stored at scripts/data/production/meta-data-center-myths/article.txt. BYLINE SIGNAL WORTH RECORDING: the author line is an outside "Software Developer and Content Creator" hosted on Meta's newsroom rather than a Meta corporate communications author line, and the piece is written in the first person about site visits Meta evidently arranged ("the two types of Meta data centers that I have visited over the past few months", "I visited an infra lab"). That is a sponsored-content-adjacent signal. The post nowhere discloses whether the author was paid, sponsored or commissioned, and this Short therefore attributes every claim to Meta or to "the post" or to "the author" and asserts none of it as established fact. WHAT THIS STORY IS: this is NOT a product launch and NOT an announcement. It is CORPORATE ADVOCACY, Meta rebutting public criticism of its data centers, on Meta's own newsroom, using figures Meta supplied about itself. The scorer gave it no launch-verb credit, which is correct. The news event is that Meta is publicly pushing back and that we can now read exactly what it claims and exactly what it does not show. TRANSCRIPTS: ZERO corroborating YouTube transcripts were captured for this story, because yt-dlp is out of date on this host; transcripts.json holds an empty videos array. That is a known tooling problem and not a content problem, and THIS SINGLE FIRST-PARTY ARTICLE IS THEREFORE THE SOLE FACT SOURCE FOR EVERY NARRATED CLAIM in this Short. No secondary reporting, no wire story, no utility statement, no regulator filing, no community group response and no independent verification of any kind was fetched or checked, and nothing is narrated as though it had been. TIMELINE PROBES: timeline-probes.json (fetched 2026-10-08T17:04:07.138Z) was inspected for ANGLE ONLY and contributed NO FACTS WHATSOEVER. Its thirteen probe titles are "The problem with data centres" (20VC with Harry Stebbings, 2025-02-22), "I Live 400 Yards From Mark Zuckerberg's Massive Data Center" (More Perfect Union, 2025-03-27), "BI investigated the footprint of 1k+ datacenters to see real-life consequences of ai" (Business Insider, 2025-07-07), "Meta announces massive 'Prometheus' and 'Hyperion' data center plans" (CNBC Television, 2025-07-14), "Exposing The Dark Side of America's AI Data Center Explosion" (Business Insider, 2025-09-12), "Why Meta is Selling Data Centers (and Why You Should Care)" (AI Insider, 2025-09-29), "Why are data centers so controversial?" (Change.org, 2025-10-28), "I Worked At A Google Data Center: What I Saw Will Shock You." (More Perfect Union, 2026-01-09), "Why Tech Companies Are Quietly Cancelling AI Data Centers" (Economy Media, 2026-05-22), "Meta's Temple data center goes live amid community concerns over water use and expansion" (25 News KXXV, 2026-07-23), "Meta, BlackRock partner on data center" (KTSM 9 NEWS, 2026-07-28), "Meta's giant AI data center bet" (Yahoo Finance, 2026-07-29) and "How AI Data Centers Are Making Everything More Expensive" (Business Insider, 2026-08-29). NOT ONE OF THEM ANNOUNCES, QUOTES OR REFERENCES TODAY'S POST, and none was fetched, transcribed or used as a fact. They are useful only as evidence that the criticism Meta is rebutting is real and pre-existing, in particular the water-use community concern probe and the consumer-energy-cost probe, which line up with Myth #1 and Myth #2 respectively. BUT THE POST ITSELF NAMES NO CRITIC, NO STUDY AND NO REPORT, so this Short never states who Meta is answering. NOTE ON GEOGRAPHY: this qualifies for our United States focused channel on the source's own terms. Meta is a US company, the only named jurisdiction in the post is Louisiana, the water benchmark is explicitly a US one ("an average US golf course"), and the workforce program is named "America's Workforce Academy". Narration speaks only Meta, Louisiana and Inboxsmith as proper nouns. Our capture checklist records that the page offers eight non-English locale variants; that is ordinary publisher site chrome and NOT a regional story signal, and no locale string appears in the stored extraction. CHROME EXCLUSION: the stored extraction is clean body prose, so the enormous navigation, locale, store, help-center and footer menus that this publisher renders around every post contributed nothing and are excluded in full, as are the "Recent News" and "Related News" cards. Those cards are DIFFERENT STORIES and NONE SUPPLIED A CLAIM, A FIGURE, A QUOTE OR A FRAMING here, and they are named explicitly so this exclusion is auditable: "Why Data Centers Are Such a Big Part of Meta's AI Approach", "Find Your Community With Forum, a Dedicated App for Facebook Groups", "Expanding Instagram's School Partnership Program to Help Teens Stay Informed", "The Future Is for Everyone: Muse for Small Business", "Meta's Kansas City Data Center and Upcoming AI-Optimized Data Centers" and "How Meta's Data Centers Drive Economic Growth Across the US". The only in-body hyperlinks in the post are the anchor "liquid cooling", pointing at Meta's own earlier cooling explainer, and the anchor "America's Workforce Academy"; neither target was fetched and neither supplied a fact. INJECTION CHECK: article.txt and the probe titles were treated throughout as UNTRUSTED DATA informing facts only, and NEVER as instructions. No string anywhere in the capture or in the probe titles addresses this agent, asks it to change its behaviour, reveal anything, adopt a persona, generate persuasive or promotional copy, or disregard its instructions. The instruction-like strings associated with this publisher's pages are ordinary page furniture and marketing calls to action, namely "Skip to content", "Dismiss locale prompt", "Listen to Article", "Pause", "DOWNLOAD ALL IMAGES", "Share this article", "Follow Meta Newsroom", "Learn more", "I Agree" and "Back to Newsroom"; none of them appears in this clean extraction and in any case NONE WAS FOLLOWED. The nearest thing to an imperative inside the body text is the author's own framing of his purpose, verbatim: "Today, I want to address some of these myths, not to create division or try to win an argument, but instead to inform and clear up some misconceptions that are quite common within the conversation of technology and AI at the moment." That is persuasive first-person advocacy by the source and was handled as a fact to describe and attribute, not as a request to act on, and its idiom "win an argument" is never spoken. One probe title, "I Worked At A Google Data Center: What I Saw Will Shock You.", is clickbait phrasing in untrusted data and did not influence the title candidates, none of which uses a curiosity gap.)