US state PFAS product restriction effective dates by category

State-by-state PFAS product ban and restriction effective dates. Each record is one state’s ban on one product category, with the effective date, the statute or bill number, the enforcement agency, and any exemptions (e.g. currently unavoidable use). Answers 'can I sell [product] containing PFAS in [state] after [date]', 'which states ban PFAS in cookware', 'when does [state] ban all PFAS products'. Roughly 30 jurisdictions with active or pending PFAS product restrictions as of mid-2026, each with different product category definitions and phase-in schedules.

The data

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 3 sources this dataset was assembled from.

• nontoxiclab.comhttps://nontoxiclab.com/pfas-state-ban-tracker-2026/
• multistate.ushttps://www.multistate.us/insider/2026/1/22/forever-chemicals-face-sweeping-bans-as-states-pass-pfas-laws-in-2025
• maine.govhttps://www.maine.gov/dep/spills/topics/pfas/PFAS-products/index.html

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup state-pfas-product-restrictions state=Washington

npx -y refsource lookup state-pfas-product-restrictions state=Washington

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "US state PFAS product restriction effective dates by category", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `state-pfas-product-restrictions`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

101 records. last verified against source 2026-08-14. due for re-check by 2026-11-12.

Licence. unknown