Maximum legal vehicle size and weight limits by US state

For each US state, the maximum legal dimensions and gross weight a vehicle plus load may have on state highways before an oversize/overweight permit is required, from the state's own vehicle code or DOT/DMV page: width, height, semitrailer length, combination length, and gross weight. Height genuinely fragments — 13 feet 6 inches in most eastern states (Florida, Ohio), 14 feet in western states (Washington) — so a load legal in one state needs a permit in the next. Answers 'how tall can a truck be in [state]', 'what is the maximum legal trailer length in [state]', and 'at what point do I need an oversize permit in [state]'. Values verbatim from statute or the agency page; the many exceptions (auto transporters, safety devices, RVs) stay in the source quote, not in extra fields.

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 7 sources this dataset was assembled from.

• dot.ca.govhttps://dot.ca.gov/programs/traffic-operations/transportation-permits
• leg.state.fl.ushttp://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0300-0399/0316/Sections/0316.515.html
• codes.ohio.govhttps://codes.ohio.gov/ohio-revised-code/section-5577.05
• txdmv.govhttps://www.txdmv.gov/motor-carriers/oversize-overweight-permits/texas-size-weight-limits
• app.leg.wa.govhttps://app.leg.wa.gov/RCW/default.aspx?cite=46.44.020
• app.leg.wa.govhttps://app.leg.wa.gov/RCW/default.aspx?cite=46.44.010
• app.leg.wa.govhttps://app.leg.wa.gov/RCW/default.aspx?cite=46.44.030

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 truck-size-weight-limits-by-state state=California

npx -y refsource lookup truck-size-weight-limits-by-state state=California

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 "Maximum legal vehicle size and weight limits by US state", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `truck-size-weight-limits-by-state`) 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.

5 records. last verified against source 2026-08-18. due for re-check by 2027-08-18.

Licence. unknown