Five states stay at 0%
Delaware, Montana, New Hampshire, and Oregon have no statewide sales tax. Alaska also has no state sales tax, though local sales taxes can still apply.
Estimate tax, compare states, and see how state plus local ranges change your final total.
Midpoint blends the available combined-rate range when a state has local variation.
Comparison uses the midpoint of each state's available combined range.
Delaware, Montana, New Hampshire, and Oregon have no statewide sales tax. Alaska also has no state sales tax, though local sales taxes can still apply.
When you only know the state and not the exact city, midpoint is usually the cleanest budgeting assumption before switching to a max-rate buffer.
Some states have modest statewide rates but meaningful local add-ons. That is why this tool compares combined ranges instead of pretending one statewide checkout rate fits every city.
Buying in a no-state-sales-tax state can reduce in-person checkout cost, but online sellers on eBay, Etsy, Amazon, or Shopify often still deal with destination-based tax collection rules where the buyer lives, not just where the seller is based.
Choose a state and amount to calculate your tax and final total.
Use minimum, midpoint, or maximum local assumptions when your state has wide local variation.
Compare up to three states using the same purchase amount and year.
Shows the state rate, available local range, combined range, and estimated tax on your current amount.
| State | State Rate | Local Range | Combined Range | Estimated Tax |
|---|
Tax is purchase amount times the chosen combined rate. Combined rate is state rate plus the selected local assumption.
Sales tax = Purchase amount x Combined rate
Combined rate = State rate + Local scenario rate
Total after tax = Purchase amount + Sales tax
Sales-tax planning gets more useful when you separate the planning estimate from final address-level checkout reality.
The midpoint is a practical planning assumption when you know the state but not the exact city or district yet.
If you are pricing inventory, budgets, or car-buying scenarios, the maximum combined range gives a conservative ceiling.
In some states the statewide rate is only part of the story. Local districts can widen the real checkout number materially.
This calculator uses year-specific state sales-tax ranges normalized from Avalara's published state rate pages for 2025 and 2026. It is designed for state-level planning, side-by-side comparison, and rough checkout estimation, not for address-level tax jurisdiction lookup or product-specific taxability decisions.
Used for the 2026 state rate, local range, and combined range dataset displayed in the calculator and all-state table.
Open the 2026 Avalara state sales tax tableUsed for the 2025 comparison dataset so users can switch years and compare broad range changes without live refetching.
Open the 2025 Avalara state sales tax tableThe calculator intentionally models state-level ranges. Final tax at checkout can differ based on local district boundaries, destination sourcing rules, and the taxability of the product being sold.
Short answers on how to interpret state, local, and combined sales-tax ranges.
Many states allow local counties, cities, or special districts to add tax. The page therefore shows minimum and maximum combined rates instead of pretending there is one universal checkout rate statewide.
Midpoint is a planning estimate between the published minimum and maximum combined rate for a state. It is useful when you know the state but not the exact buying location yet.
No. This is a state-comparison and planning tool. Final tax at checkout can still depend on the exact jurisdiction and product taxability rules.
Some states have no local sales tax or effectively fixed statewide totals for general planning purposes, so the local contribution does not widen the range.
The tool currently supports 2025 and 2026 and is built so later years can be added through the same local-cache loader workflow.
The page pulls the year-specific state sales-tax dataset from Avalara, writes the normalized result into a local app cache on first request, and reuses that local file afterward.