Is Software Taxable? Sales Tax on Software by State

TL;DR

Whether software is taxable depends on two things, the state where your customer sits and how you deliver the product. The software itself is not inherently taxable or exempt.

• Downloaded or licensed software counts as tangible personal property in most states that tax it, so it usually carries sales tax the same way a physical good would.

• SaaS and cloud-hosted access vary widely by state, taxed as a service in some, taxed as property in others, and fully exempt in the rest.

• The state-by-state table below gives you the exact treatment for each delivery method, with a Department of Revenue citation for every row.

• Selling into many states means you owe tax per customer, not one rule of your choosing. See the multi-state section below.

Is downloaded software taxed differently than SaaS?

Every state that taxes software sorts your product into one of two tracks before it decides whether you owe anything, and the track it picks depends on how the software reaches the customer. Downloaded or licensed software follows one set of rules. SaaS and cloud-hosted access follow another. The same functionality can land on either side, which is why a single blanket answer to "is software taxable" never holds up.

Downloaded and licensed software maps to tangible personal property in most states that tax it, because those states wrote their sales tax laws decades before anyone shipped code over the internet. A boxed program on a disk was clearly a good, and when the disk disappeared and the download replaced it, most revenue departments kept treating the transaction as a sale of property. States like Texas and Washington still classify a downloaded license the way they classify a physical item you buy at a store. If your state taxes tangible personal property, and most do, downloaded software usually falls inside that net.

SaaS breaks the pattern because there is no property to point at. The customer never takes possession of anything. They pay for access to software running on someone else's servers, so states have to decide whether that access counts as a taxable service, as tangible personal property anyway, or as nothing taxable at all. New York taxes SaaS as tangible personal property. California generally exempts it. Texas taxes it as a data processing service, then exempts a portion of the charge. Three states, three different answers to the identical product.

What drives every one of these outcomes is the legal classification the state assigns, not what the software actually does for the buyer. A revenue department does not ask whether your product manages payroll or edits video. It asks how the software was delivered and which statutory category that delivery falls into. Two products with identical features get taxed differently when one ships as a download and the other as a subscription. The table below keeps downloaded software and SaaS in separate columns for exactly this reason, because collapsing them into one answer would be wrong in most states.

What is the sales tax on software in each state?

Every state that levies a sales tax makes two separate decisions about software, one for downloaded or licensed products and one for SaaS or cloud-hosted access. The table below splits those decisions into their own columns because a state that taxes a downloaded program does not automatically tax the same functionality delivered as a subscription. Read each row as two answers, not one.

The rows are grouped by pattern so you can find your situation fast. The first group taxes both delivery methods. The second taxes downloaded software but exempts SaaS. The third exempts both. Every row links to that state's Department of Revenue guidance, because taxability rules change through rulings and legislation, and the DOR page is the version that holds up on audit.

States that tax both downloaded software and SaaS

States that tax downloaded software but exempt SaaS

States that exempt both

Treat this table as a starting map, not a filing instruction. Several states carve out exemptions for business-use SaaS, resale, or specific industries, and the DOR link for each row is where those conditions live. Confirm the current rule against the source before you charge or remit.

States with no general sales tax

Oregon, Montana, New Hampshire, and Delaware sit outside the state-by-state table above because they charge no general sales tax at all, so downloaded software and SaaS both ship to customers there tax-free. You still track those customers for revenue and nexus purposes, but no sales tax attaches to the transaction.

Alaska is a fifth state with no general sales tax, and the exception that trips people up. Alaska has no statewide sales tax, but individual boroughs and municipalities levy their own local rates, and many now tax remote sales through the Alaska Remote Seller Sales Tax Commission. A SaaS sale to a customer in Juneau can carry local tax even though the state itself imposes none. Treat Alaska as a live jurisdiction with local rules, not a clean exemption like the other four.

Why does the same software get taxed two different ways?

The delivery mechanism decides how a state taxes software. A company can buy accounting software as a perpetual license installed on its own machines, or it can subscribe to the identical accounting functionality hosted in the vendor's cloud. Many states tax the first transaction and treat the second one entirely differently, even though the buyer ends up doing the same work with the same features.

The split comes down to how each state classifies what changed hands. When you buy a perpetual license, several states treat the transferred software as tangible personal property, the same category as a physical good, so the sale gets taxed like a purchased item. When you subscribe to that functionality as SaaS, no property transfers to you. You pay for remote access to software the vendor still controls, and a state that taxes goods but not services can land on a different answer for the subscription.

Texas taxes both the license and the SaaS access, treating cloud software as a taxable data processing service. California taxes the downloaded license as tangible personal property but generally exempts SaaS because no property changes hands. Same product, same buyer, two outcomes driven purely by how the buyer receives it.

That divergence is why the state-by-state table above needed two columns instead of one. A single "is software taxable" answer per state would hide the exact distinction that determines your liability. A vendor who reads only the downloaded-software column and assumes it applies to their SaaS product can undercharge tax for years, then face the gap on audit. Read both columns for every state where you have customers, and match each one to how you actually deliver the product.

How do you handle sales tax when selling software in multiple states?

A company selling software into twenty states owes tax under twenty different rulebooks. Each customer's state decides whether the sale is taxable, and the delivery method decides which column of that state's rules applies. A perpetual license sold to a buyer in Texas follows Texas rules for downloaded software. The same product sold as a subscription to a buyer in Ohio follows Ohio's treatment of SaaS. You do not get to standardize on the rule you like best, because the customer's state holds the taxing authority.

The complexity compounds because states also disagree on when you owe them anything at all. Economic nexus thresholds vary by state, often set at a dollar amount of sales or a count of transactions, and crossing that threshold in a given state triggers a collection obligation there. A seller can owe tax in a state it has never physically entered simply by selling enough software to customers who live there. Tracking which thresholds you have crossed, in which states, for which delivery methods, becomes a live calculation that changes every month as your customer base shifts.

Manual tracking collapses at this scale for a specific reason. A spreadsheet captures the rules as they stood the day someone built it, and state Departments of Revenue update guidance, thresholds, and taxability classifications on their own schedules. Ohio can reclassify a category, a new state can lower its nexus threshold, and your spreadsheet keeps applying last year's answer to this year's sales. Nobody notices until the gap surfaces.

The gap surfaces during an audit, and by then it covers a period you can no longer fix. An auditor reviews several years of transactions against the rules that applied at the time, and every sale where you charged the wrong rate or failed to collect becomes uncollected tax you now owe out of pocket, plus penalties and interest. You cannot go back and bill customers from three years ago. Getting multi-state taxability wrong creates a balance-sheet liability that outlasts the sales that caused it.

How does Taxwire keep multi-state software sales tax correct?

Taxwire's engine holds the taxability rule for every state and delivery-method combination, so a Texas download and an Ohio SaaS subscription each hit the correct treatment automatically instead of running through a rule a finance team maintains by hand. The distinction the earlier sections drew becomes the exact input Taxwire tracks, customer by customer, across every state where you have a filing obligation.

State rules change, and they change in ways that are hard to catch when you are running a company. A state that exempted SaaS last year can start taxing it, or a Department of Revenue can issue new guidance that reclassifies cloud access as a service. Taxwire's in-house tax team tracks DOR guidance and legislation as each state publishes it and updates the underlying rule set directly, so a transaction processed today reflects this month's classification rather than whatever a spreadsheet owner last confirmed.

Audit exposure is the reason this matters more than admin convenience. When an auditor reviews a lookback period, they check whether you charged the correct treatment on every sale in every state during those years, not whether your process is tidy now. Taxwire keeps a record of the taxability decision applied to each transaction and the DOR basis behind it, so you can show why a given sale was taxed or exempted rather than reconstructing that reasoning under pressure.

For a company selling into twenty or more states, that continuous mapping replaces the spreadsheet that quietly falls out of date. You get taxability that reflects each customer's state and delivery method on every invoice. See how it works at Taxwire.

What this guide does not cover

This guide covers US state sales tax only. It does not address EU VAT, and it makes no claim that hosting servers or CDN nodes in the EU creates a VAT registration obligation. VAT liability turns on place-of-supply rules, which look at where your customer is located and what you sell, not where your infrastructure sits. That is a separate legal question with its own thresholds and filing mechanics. If you sell into the EU, treat it as a distinct analysis rather than an extension of the state-by-state rules above.

FAQ

Is SaaS taxable? SaaS is taxable in some states, exempt in others, and treated as tangible personal property in a few, so the answer depends entirely on where your customer is located.

Is downloaded software taxable? Downloaded or licensed software is taxable in most states that levy a sales tax, because those states classify it as tangible personal property regardless of how it reaches the buyer.

Is custom software taxable? Custom software written for a single client is exempt in many states that tax off-the-shelf software, since states often treat the custom work as a nontaxable service rather than a sold good.

Does software delivery method change the tax? Yes, a perpetual license and a SaaS subscription of the same functionality can carry different tax outcomes in the same state, because states key their rules to delivery mechanism rather than product function.

Do I owe tax based on my location or my customer's? You owe tax based on each customer's state and delivery method, so a company selling into twenty states tracks up to twenty separate rule sets.

Does this apply to EU VAT? No, VAT follows place-of-supply rules and sits outside US state sales tax, so nothing here answers whether you owe VAT.