Can You Work a Remote Job in Another State? Where You Pay Taxes, Explained

You can physically work from any state, but your employer usually cannot employ you in any state. Once a company hires someone in a new state it has to register with that state's tax and unemployment agencies, withhold the right income tax, follow that state's leave and overtime rules, and usually carry workers' compensation there. That administrative footprint is why a fully-remote listing still says "must reside in one of these 14 states." The restriction is about the employer's back office, not about your ability to do the job.

On taxes, the short answer is that you pay where you live. A remote employee owes state income tax to their state of residence, because that is where the work is physically performed, and the employer withholds accordingly. The exception is the convenience of the employer rule, used by a handful of states including New York, which can tax you on the same wages your home state is already taxing. The state-by-state detail is below.

There are two exceptions worth knowing immediately. Independent contractors face far fewer state restrictions, because a 1099 contractor handles their own filings and does not create a payroll registration for the company. And larger employers, or ones using an employer of record, often hire in all fifty states because the overhead is already paid for. Everything below explains where the lines actually fall.

If I work remotely from another state, where do I pay taxes?

As a general rule, you owe state income tax where you physically perform the work, which for a remote employee is where you live, not where your employer's office sits. Your employer withholds for your home state, you file one resident return, and that is the end of it. This is the situation for the large majority of remote workers, and it is genuinely simple.

Two things change that answer. If your employer is based in a convenience-rule state, you can owe tax to that state as well as your own. And if you move mid-year, you file part-year returns in both states. Neither is common, but both are expensive to discover late.

It stops being simple in two cases. The first is a mid-year move, which usually means part-year resident returns in both states. The second is the convenience rule, which is the one that catches people out.

The convenience of the employer rule, explained

A small group of states tax you on income from an employer based in their state even when you never set foot there. The logic is that if you work remotely for your own convenience rather than out of your employer's genuine business necessity, the income is sourced to the employer's state. New York is the most aggressive enforcer, and in 2025 the Tax Appeals Tribunal upheld the rule in the long-running Zelinsky case, finding that ordinary remote work does not count as employer necessity. New York publishes the actual test in memorandum TSB-M-06(5)I, and the escape route it defines is set out on our page on state tax withholding for remote employees.

If your home state has an income tax, you usually get a credit for tax paid to the employer's state, so the practical damage is limited. The painful case is living in a state with no income tax and working for a New York employer: there is no home-state return to claim a credit on, so you simply pay New York tax with nothing to offset it. The nine states with no broad personal income tax in 2026 are Alaska, Florida, Nevada, New Hampshire, South Dakota, Tennessee, Texas, Washington and Wyoming. Moving to one of them does not help if your employer sits in a convenience-rule state.

None of this changes how much the job pays. It changes your take-home, which is exactly why you want to know the employer's state before you sign, not in April.

Why employers limit which states they hire in

Put yourself on the finance side for a minute. Adding one state typically means a revenue department registration, an unemployment insurance account, a workers' compensation policy or endorsement, a payroll system configuration, and an ongoing filing calendar. Then come that state's specific obligations: paid sick leave accrual, final paycheck timing, meal break rules, notice requirements, and in a growing number of states, mandated retirement plan participation. For a company of forty people, opening a state for one hire can cost more in the first year than the hire saves.

So they draw a list. Typically it is the states where they already have someone, plus whichever ones the founders live in. That list has nothing to do with your resume, which is worth remembering when a role you are perfect for rules you out geographically. Employers who work through an employer of record skip the whole problem by renting someone else's legal entity, which is why some small companies genuinely do hire in all fifty states. It is always worth one question.

Employers dealing with this from the other side can read our breakdown of hiring remote employees in another state, which walks through registration, nexus and the sequence to do it in.

Does pay change depending on which state you live in?

Less than it used to. Remote-first employers increasingly run a single national pay band for a role, because location-adjusted pay creates awkward internal comparisons and loses candidates to competitors who do not bother. Where location still bites is tax: the same $120,000 offer leaves you with noticeably more in Texas than in California, and that gap is often larger than any geographic pay adjustment would have been.

State law is pushing in the same direction. As of 2026, 18 states plus Washington, D.C. have pay transparency laws on the books, and the ones that require the range in the posting itself now include California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont and Washington, with Virginia joining on July 1, 2026 and Maine on July 29, 2026. Delaware follows in September 2027. The detail that matters for remote roles: if a job can be performed from a state with a posting requirement, that state's law generally applies no matter where the employer is headquartered. In practice a national remote listing has to publish a range, which is why so many more of them now do.

That is good news if you are negotiating, because it means the number is checkable. Employers that build defensible pay bands before posting tend to hold firm on the range and negotiate on level instead, so arguing about title and scope usually gets you further than arguing about the number. Every listing on this board carries a published range for the same reason: you should be able to decide whether a role is worth an application before you spend an hour on it.

What about jobs that require a license?

Licensing is the one area where "any state" is genuinely false, and it is not negotiable. Registered nurses, therapists, CPAs, attorneys, insurance adjusters and teachers are licensed state by state, and a remote role does not change that. Some professions have interstate compacts that let one license travel, and some do not. If your field is licensed, the state list on a remote listing is a hard legal requirement rather than a preference, and no amount of enthusiasm in a cover letter will move it.

Roles that are not licensed, which is most of them, only ever face the payroll question. Support, engineering, design, marketing, bookkeeping, operations and administrative work all fall in that bucket.

Contractor or employee changes the whole answer

If you are engaged as a 1099 contractor, the employer is not running payroll for you, so there is no state registration to trigger and generally no state restriction to satisfy. You invoice, you pay your own self-employment tax, and you file in the state where you live. That freedom comes at a real price: no employer-side payroll tax contribution, no unemployment insurance, no company health plan and no paid leave, which is why contractor rates need to be meaningfully higher than the salaried equivalent to break even. We put numbers on that trade in our comparison of remote 1099 vs W-2 jobs.

Be careful with the reverse situation. If a company classifies you as a contractor purely to dodge registering in your state, while controlling your hours, tools and how you do the work, that is misclassification, and it is the company's legal exposure rather than yours. The tell is a full-time schedule with a contractor agreement and no other clients.

What hiring remote employees in other states costs an employer

One out-of-state remote employee is enough to create a payroll tax presence for the employer in that state. There is no minimum headcount and no grace period: the obligation attaches to the first hire. That single fact explains most of what job seekers experience as an arbitrary state list, and it is worth understanding from the employer's side even if you are the one applying.

Here is what actually gets triggered when a company hires its first person in a new state.

Individually none of these is large. Together, and multiplied across a filing calendar somebody has to own, they are why a forty-person company decides it will hire in nine states and not fifty. Larger employers and anyone using an employer of record have already absorbed the cost, which is why they list every state.

If you are on the hiring side of this, the practical decision is whether to open the state, use an employer of record, or engage the person as a contractor, and the answer usually turns on how many more people you expect to hire there. We cover the mechanics in hiring remote employees in another state, the loaded numbers in what it costs to hire a remote employee, and the whole process in how employers hire remote workers. Back-office roles are where this comes up most often, since finance and support hires are frequently the first person a company employs outside its home state: see hiring a remote bookkeeper for a worked example of the same decision.

Can I work remotely from another state without telling my employer?

You can physically do it, but you should not, because the exposure lands on you as well as on the company. Working from a state your employer is not registered in means their withholding is wrong for the whole period, which usually surfaces as an unexpected tax bill for you rather than for them. It can also void their workers' compensation coverage for you and, in some states, breach their insurance terms.

The version that causes real damage is the quiet permanent move. Payroll keeps withholding for your old state, your new state expects a resident return it never receives, and you end up filing amended returns in two states while explaining a timeline you would rather not discuss. Companies increasingly detect this anyway, through VPN geolocation, device check-in data or the address on an expense claim.

Short trips are a different question and are usually fine. Most states have a threshold, commonly somewhere between 14 and 30 days, below which a visiting worker creates no filing obligation, though a handful start counting at day one. A two-week working holiday is rarely a problem. Three months at a relative's house in another state is a move, whatever you call it internally. If you want to relocate, ask first: a company that cannot employ you in the new state will often support a contractor conversion or an employer-of-record arrangement rather than lose you.

How to ask about state eligibility without hurting your chances

Ask early, ask plainly, and ask in writing. A recruiter would much rather answer this in the first exchange than discover it after three interview rounds, and asking signals that you understand how remote employment works. One line does it: "I am based in Ohio. Are you set up to hire there, or do you work with an employer of record?"

Three follow-ups worth getting answers to before you accept anything:

• Which state is the employing entity in? This is the question that surfaces a convenience-rule problem while you can still price it into your salary ask.
• Is the role W-2 or contract? It determines your tax filing, your benefits and roughly 20 to 30 percent of your effective compensation.
• What are the required overlap hours? A lot of what looks like a location requirement is really a timezone requirement, and timezone is far more negotiable than payroll registration.

If the state list rules you out, do not spend the application. Filter instead: our remote jobs near me page shows the roles posted in the last seven days that are open to candidates across the United States, and remote jobs usa carries the full US-eligible board. Both publish the salary range on every listing so you can rule things in or out in seconds.

The short version

You can work from any state you like. Your employer needs a reason and a budget to employ you there, and that is what the state list on a listing is really telling you. Check the employing entity's state against the convenience-rule list, confirm W-2 or contract, treat licensure as immovable, and ask about an employer of record when a role is otherwise a fit. None of it is complicated once you know which question you are actually asking.