Moonlighting and Side Projects on H-1B: Where the Legal Line Actually Is

H-1B lets you hold exactly one employer's job — but passive income, open source, and the right structures can keep your side project alive legally.

You built an app over the last six months. It's on the App Store. Users are actually paying for it. And then the thought hits you at 11 p.m.: is this going to get my H-1B revoked?

This fear is completely rational. H-1B is an employer-specific visa. You are authorized to work for exactly one employer — the one named on your approved I-129 petition. Everything outside that relationship is governed by a set of rules that immigration attorneys debate, USCIS adjudicators interpret inconsistently, and almost no one explains clearly to the people who need to know. This guide does exactly that.

The foundational rule: H-1B is employer-specific

The H-1B program is structured around the Labor Condition Application (LCA) that your employer files with the Department of Labor. That LCA certifies a specific job, a specific worksite, and a specific prevailing wage. USCIS approves your I-129 based on that LCA. Your authorization to work in the US is therefore tied to performing that job, for that employer, at the wages and conditions DOL certified.

Section 214(n) of the Immigration and Nationality Act, implemented in 8 CFR §214.2(h), makes this explicit. "Unauthorized employment" — performing services in exchange for remuneration for any entity other than the petitioning employer — is a status violation under 8 USC §1324a. It can result in denial of extension, denial of H-1B transfer, denial of adjustment of status (green card), or, in the most serious cases, removal proceedings.

The key phrase in that definition is services in exchange for remuneration. Not all income is employment. Understanding that distinction is the entire game.

What is and isn't "employment" under USCIS rules

The immigration bar broadly agrees on the extremes. The 1099 consulting gig for a client you invoice monthly is unauthorized employment. The S&P 500 index fund paying dividends is clearly not. The app revenue falls somewhere in between and depends heavily on how the income flows.

The passive income doctrine and why it matters for app revenue

The concept of "passive income" does not appear verbatim in the H-1B statute, but it underpins how practitioners analyze side income. The logic goes like this: the H-1B restriction covers services in exchange for remuneration — an employment relationship. Passive income — returns that flow to you as a capital owner without requiring you to perform ongoing services — does not create an employment relationship. Therefore it falls outside the unauthorized employment prohibition.

For a mobile app, the analysis turns on whether the revenue is genuinely passive or whether it requires your ongoing labor. An app you built, launched, and now runs largely automatically — processing payments, delivering content, requiring no significant ongoing development time on your part — has a reasonable argument for passivity. An app that you actively support, update weekly, handle customer service for, and treat as a business requiring your regular working hours looks more like employment.

In practice, no bright line exists. If USCIS were reviewing your situation, they would look at: how many hours per week you spend on it, whether any income flows to you personally vs. through a corporate entity, whether you call yourself a "developer" or "contractor" anywhere, and whether the app competes with or is adjacent to your H-1B employer's work.

The corporate wrapper strategy — and its real limits

The most commonly cited approach for H-1B holders who want to build and monetize side projects is to incorporate a separate entity — typically a C-Corp or an LLC taxed as a corporation — hold the app or IP in that entity, let the entity receive all revenue, and avoid taking any salary or W-2 compensation from the entity.

The argument is: you are a passive investor and owner. The entity earns the revenue. You receive distributions (treated as investment return, not wages). You do not "work for" the company in an employment-law sense.

This argument has real merit and is supported by immigration attorneys who regularly advise H-1B holders. But it also has genuine limits:

1. You cannot be the company's employee. No W-2. No 1099 from the company to yourself. No officer salary. This is the most important constraint. The moment you pay yourself for services — even under a professional services contract between you and your own LLC — you have created an employment relationship that requires a separate H-1B petition.

2. Equity distributions are not automatically safe. If the company is an S-Corp, LLC, or pass-through entity and the IRS characterizes the distributions as self-employment income, immigration counsel needs to evaluate whether that creates an employment nexus. C-Corps are cleaner because dividends are categorically different from wages.

3. "Owner" activity can become employment. If you are the sole employee, the sole developer, the sole customer service rep, and the sole decision-maker, USCIS adjudicators and federal courts have sometimes pierced the corporate structure and found that the individual was performing services for the company — not merely holding equity. The Neufeld Memo on H-1B employer-employee relationships (2010) is the canonical reference here, even though it primarily addressed staffing companies.

4. You still need to report the income. Passive income from a corporation you control must be reported on your taxes. An I-485 adjudicator reviewing your green card application can and will look at tax returns. Unexplained income streams are a red flag.

For a deeper look at starting a company while on an immigration visa, see our guide on starting a company on F-1, OPT, or H-1B and the companion post on LLC vs. C-Corp structures for international founders.

Concurrent H-1B: the legitimate path to a second income stream

If you want to work for a second employer — including your own company, structured as an employer — the correct answer is a concurrent H-1B petition. Your primary employer holds your existing H-1B. The second employer (or your company, if it is genuine enough to file as an employer) files a separate I-129 petition with a new LCA, naming you as the beneficiary.

Both petitions can be valid simultaneously. There is no limit on the number of concurrent H-1B petitions you can hold. The hours across both positions can add up to more than 40/week in principle, though DOL expects each LCA to reflect the actual hours for that role.

The practical constraint: your own early-stage startup almost certainly cannot file a valid H-1B petition for you. The Neufeld Memo requires a legitimate employer-employee relationship where the employer has actual control over the work. If you are the founder, sole employee, and primary decision-maker, you cannot control yourself in the employment law sense. Some structures — with an independent board, outside investors, and governance documents that give others control — can satisfy this test, but it is expensive and complicated.

Read more about how concurrent employment works in our detailed breakdown at concurrent H-1B and second job guide.

What the gray zone actually looks like in practice

Here are four common scenarios and honest assessments of each:

Scenario 1: App with $500/month in App Store revenue

You built a utility app two years ago. It earns passive subscription revenue. You spend maybe two hours a month reviewing crash logs. Revenue flows through your single-member LLC.

Risk level: Low-to-moderate. Two hours a month is credibly passive. Revenue through an LLC adds a layer of structure. The main exposure is if you ever characterize yourself as the app's developer in a context that gets reviewed (LinkedIn, a visa interview, a green card application). Keep your involvement minimal and documented. Do not pay yourself.

Scenario 2: Freelance consulting on weekends, 10 hours/week

A former colleague pays you $150/hour to help architect their startup's backend. You invoice them monthly as an independent contractor.

Risk level: High. This is textbook unauthorized employment. Services, remuneration, ongoing relationship, invoicing. A concurrent H-1B or a simple "not doing this on H-1B" is the only safe answer. See our full treatment at freelancing and 1099 work on F-1, OPT, and H-1B.

Scenario 3: SaaS product with $8,000/month revenue, you're the sole developer

You run a B2B SaaS tool. You actively develop features, handle customer support tickets, and bill clients monthly. You take no salary but the LLC distributes profits to you quarterly.

Risk level: High. This is a high-activity business. The "passive investor" argument is very difficult to sustain when you are the sole source of the product's ongoing value. A USCIS site visit or a green card adjudicator reviewing your tax history would likely find that you are performing services for this entity.

Scenario 4: Mobile game earning ad revenue, built before your H-1B

You released a mobile game on OPT. It earns $200-$400/month in ad revenue automatically. You have not updated it in 18 months. Revenue flows to a C-Corp you own.

Risk level: Low. The work was done pre-H-1B. The revenue is genuinely passive. C-Corp dividends are not wages. Your ongoing involvement is near-zero. This is probably the cleanest scenario for app revenue on H-1B.

Common mistakes

• Taking a 1099 payment "just once." There is no de minimis exception to unauthorized employment in the H-1B statute. A single payment for services is a status violation.

• Assuming the LLC makes it fine. The corporate structure helps, but it is not a blanket immunity. What matters is whether you are providing services, not what legal entity receives payment.

• Using LinkedIn to advertise your side business as a freelancer or consultant. USCIS FDNS site visitors and consular officers do check LinkedIn. Being listed as "Freelance Developer" or "Independent Consultant" while on H-1B is a documentation problem.

• Ignoring the green card implications. Even if USCIS doesn't catch unauthorized employment during your H-1B period, the I-485 application for adjustment of status asks directly about unauthorized employment. A "no" that your tax returns contradict can result in denial and a permanent bar.

• Working remotely for a foreign employer. This is a common misconception: that working for a non-US company avoids US unauthorized employment rules. Wrong. If you are physically present in the US performing services for any employer not on your I-129, it is unauthorized employment regardless of where the employer is incorporated or where the payment originates. See our full analysis in the remote work and H-1B guide.

• Treating the corporate wrapper as a "set and forget." If the business grows and your active involvement increases, the risk profile changes even if the legal structure hasn't. Reassess annually with an immigration attorney.

A step-by-step framework for evaluating a side project

Use this checklist before accepting any compensation from work outside your H-1B employer:

1. Are you performing services in exchange for compensation? If yes, stop. This requires either a concurrent H-1B or you don't do it on H-1B.
2. Is the income passive — genuinely requiring no ongoing labor from you? If yes, proceed to step 3.
3. Does a corporate entity (C-Corp preferred) receive the income, not you personally? If no, restructure before continuing.
4. Have you confirmed with an immigration attorney that your specific situation qualifies as passive? If no, do this before the project earns meaningful revenue.
5. Do your tax returns reflect the income accurately, in a way consistent with your immigration history? If no, this creates downstream risk in green card adjudication.
6. Have you removed or updated any professional profiles (LinkedIn, GitHub bio, personal site) that describe you as a freelancer, contractor, or independent developer? If no, do this now.

How this changes across visa types

H-1B is the most restrictive common status for side income. For comparison:

• OPT/STEM-OPT: You need OPT-qualifying employment, but you can have multiple concurrent employers as long as each is related to your major and provides at least 20 hours/week during OPT. Side projects with income still need to be analyzed as employment. See OPT vs STEM OPT vs CPT.
• H-4 EAD: Employment-authorized, any employer. No secondary employment restrictions.
• O-1: Similar employer-specific restriction to H-1B. Concurrent O-1 petitions are possible.
• TN (Canada/Mexico nationals): Employer-specific, same unauthorized employment risk as H-1B.
• Green card (permanent resident): Work for anyone, start a business, earn any income. This is a major reason people prioritize green card timeline.

Frequently asked questions

Can I earn money from a side project or app while on H-1B?

It depends entirely on the structure. Revenue flowing to a corporation you own (a C-Corp or LLC treated as a corporation) where you are not performing services in exchange for compensation is generally considered passive income, not unauthorized employment. You cannot, however, pay yourself a salary or distributions as a contractor or employee of your own company. Consult an immigration attorney before drawing any income from a company you control.

What counts as unauthorized employment on H-1B?

USCIS treats unauthorized employment as performing services in exchange for remuneration for any entity other than the petitioning employer listed on your approved I-129. This covers 1099 freelance work, a second W-2 job, and consulting gigs. It does not automatically cover passive investment returns, royalties on pre-existing work, or income flowing through a separate corporate entity where you are solely an investor — but that line is genuinely narrow and fact-specific.

Is open source work or a GitHub project a problem on H-1B?

Unpaid open source contributions, personal GitHub projects, and hobby coding are not employment. No remuneration, no employment relationship. The moment you accept payment — even a one-time consulting fee or a GitHub Sponsors payout above trivial amounts — the activity starts to look like services in exchange for compensation, which can trigger unauthorized employment concerns.

Can I start an LLC or company while on H-1B?

You can form and own an LLC or corporation on H-1B. The act of incorporation is not employment. What you cannot do is work for that company as an employee or contractor without a separate H-1B petition naming that company as the petitioning employer. The company can exist, hold assets, receive passive revenue, and be funded — you simply cannot be its employee without proper authorization.

What is the actual USCIS enforcement risk for H-1B side income?

USCIS site visits (the Fraud Detection and National Security unit) focus primarily on your petitioning employer — verifying the job exists, the wage is paid, and the role matches the LCA. Side income comes to light most often through tax returns, a disgruntled employer tip, or an I-485 adjudication where USCIS scrutinizes your full employment history. The risk is not zero, and a finding of unauthorized employment is a status violation that can result in denial of future benefits or removal proceedings.

Your H-1B doesn't have to mean your side project dies — but it does mean you need to be deliberate about structure, compensation, and documentation before the income starts. If you want a second opinion on your specific situation or help finding employers who are comfortable with founders and entrepreneurs on their team, F1Jobs works with H-1B holders navigating exactly these questions every week.