Explore the H1B Database: Find Visa Records and Employer Data

Have you ever struggled to track a specific H-1B visa petition or its sponsoring employer? The H-1B database is a searchable, public record that stores case details for thousands of approved petitions, including employer names, job titles, and wage data. You can use it to research an employer’s historical sponsorship patterns or verify a case’s status by entering a case number or company name. This tool offers a clear, centralized record of past H-1B filings to help you make informed decisions.

Understanding the Visa Holder Registry

The Visa Holder Registry within an h1b database functions as a structured repository of active petition records. It links employer, beneficiary, and job data to track status changes like transfers or employer modifications. Users query this registry to verify an individual’s current visa classification and the validity period of their I-797 approval notice. The registry’s core utility lies in distinguishing between historic filings and actively maintained statuses, ensuring that searches return only legally valid employment authorizations.

What the Publicly Available Worker Records Actually Contain

The publicly available worker records within the H1B database contain specific, employer-submitted labor condition applications (LCAs) and related filings. These records disclose the beneficiary’s job title, the full legal name of the employer, and the prevailing wage offered for the position. They also list the worksite location, including city and state, and the petition’s start and end dates. Critically, records include the employer’s attestations regarding recruitment efforts, but they do not contain the worker’s personal contact details or immigration status outcomes.

• Job title and full employer company name as filed on the LCA
• Prevailing wage and proposed wage for the specific position
• Worksite address, including city and state, not the worker’s home address
• Petition validity period with specific start and end dates

How Employers and Sponsoring Companies Are Listed

In the H1B database visa holder registry, employers and sponsoring companies are listed by their legal business name, location, and unique federal ID. You can filter entries to see which organizations submit the most petitions annually, from multinational tech giants to niche startups. The registry displays the sponsor’s industry, the number of beneficiaries, and the job titles they support. For quick reference, use the table below to compare how listings vary by company type.

Company Type	Listing Focus	Common Data Field
Large Tech Firm	High volume of H-1B approvals	Multiple job categories, wide wage ranges
Small Business	Single or few sponsored employees	Specific role, precise salary data

Wage Data, Job Titles, and Work Locations in the Registry

The H1B database registry links each petition to a specific job title, work location, and prevailing wage. Wage data appears as the certified prevailing or offered salary, often broken by labor condition application (LCA) year. Job titles range from generic “Software Engineer” to niche roles like “Lead Data Architect.” Work locations are listed at the city and state level, enabling precise geographic filtering. To compare these fields, the table below shows typical registry entries:

Field	Example Entry	User Utility
Job Title	Senior Systems Analyst	Filter by occupation specificity
Work Location	San Jose, CA	Focus search by metro area
Wage Data	$140,000/year (prevailing)	Compare offered vs. certified wage

Navigating the Official LCA Disclosure Portal

Navigating the Official LCA Disclosure Portal provides a direct line to the raw H1B database, bypassing commercial aggregators. Users filter by specific employer names or fiscal years to unearth certified Labor Condition Applications.

The portal’s real power lies in viewing exact wage levels and worksite addresses, revealing patterns often hidden in summary statistics.

Directly searching this H1B database requires patience, as the interface lacks autocomplete; using exact employer legal names is crucial. You can sort results to see the highest-wage positions or verify an employer’s historical petition volume, offering a transparent, unvarnished view of the H1B landscape.

Step-by-Step Guide to Accessing Government Files

To start, head straight to the Department of Labor’s LCA Disclosure Portal. Click the “Search” button to open the query form. For a targeted H-1B database lookup, enter the employer’s name or a specific year range. Hit “Search” again, then scroll through the results to find the LCA case you need. Open any PDF to view wage data, job titles, and work locations. This method gives you direct access to raw government records without any third-party tools.

• Use the “Case Number” field if you already have the LCA ID for instant retrieval.
• Limit your search to a single fiscal year to avoid an overload of results.
• Download each PDF for offline review and cross-referencing with other H-1B data.
• Bookmark the portal’s URL for quick repeat visits when tracking multiple employers.

Filtering by Fiscal Year, Employer, or Occupation Code

The portal’s search functionality allows users to systematically narrow LCA records by applying granular filtering parameters. Selecting a specific Fiscal Year instantly isolates applications from that cycle, enabling trend analysis over time. Filtering by Employer returns all certified LCAs under that legal entity, revealing sponsorship volume and job locations. An Occupation Code filter, based on the SOC system, targets precise skill categories, such as Software Developers, excluding unrelated roles. Combining these filters—for instance, “2024 Fiscal Year” plus “Amazon” plus “15-1252”—yields a precise dataset matching that employer’s specific occupation-year record set.

Common Errors When Searching the Public Repository

A primary error is over-filtering by employer name, often using abbreviations or incomplete names that miss entire cases under legal parent entities. Users also input exact dates instead of date ranges, returning zero results for valid records. Another common mistake is selecting incorrect case statuses (e.g., “Certified-Willful” search pulling withdrawn petitions). Avoid typing full case numbers; truncated versions yield broader, accurate matches. Always clear prior search criteria before each new query to prevent unintended combined filters.

Common Errors When Searching the Public Repository: misusing employer names, restrictive date inputs, wrong status filters, and failing to reset prior criteria.

Key Data Fields in the Employment Record Set

When you pull an H1B database record, the Key Data Fields in the Employment Record Set snap into focus. You see the employer’s name and tax ID, then the precise job title—like “Software Developer” instead of vague roles. The SOC code follows, tying that title to a standardized occupation. Next come the wage fields: prevailing wage, offered wage, and the period of intended employment. These aren’t just numbers; they reveal if an employer offered the legal minimum or a premium. The work location field pinpoints where the actual labor happens—a satellite office versus the corporate HQ. Every field tells a story of compliance and intention, not abstract regulation.

Base Salary, Prevailing Wage, and Full-Time Equivalents

Within the H1B database, base salary, prevailing wage, and full-time equivalents define compensation and employment intensity. Base salary represents the annual wage an employer pledges, while prevailing wage is the legal minimum set by the Department of Labor for the position’s location and occupation. The full-time equivalent (FTE) value indicates whether a role is part-time (e.g., 0.5) or full-time (1.0), directly scaling the required salary. A fractional FTE reduces the mandated prevailing wage proportionally, altering case status.

• Base salary must equal or exceed the prevailing wage for the certified FTE.
• Prevailing wage varies by city, state, and job classification within the database.
• FTE of 1.0 implies 35–40 hours weekly; lower values indicate prorated wages.
• Discrepancies between base salary and prevailing wage signal potential underpayment.

Job Classification Under Standard Occupational Codes

In the H1B database, the Standard Occupational Classification (SOC) code is the primary field for job classification, mapping each petition to a specific role like “Software Developers, Applications” (15-1252). This code governs data normalization, enabling users to filter by job family, skill level, or industry segment. *A single SOC code may aggregate related titles with distinct salary ranges, requiring careful interpretation.*

How does the SOC code ensure accurate job classification across multiple employer filings?
It standardizes roles industry-wide, preventing employers from manually mislabeling positions and allowing direct salary and status comparisons between companies.

Worksite Addresses and Employer Legal Names

Within the H1B database, the worksite address and employer legal name provide a critical, actionable layer of verification. The worksite address pinpoints the exact physical location where the beneficiary performs labor, which frequently diverges from the employer’s headquarters. Cross-referencing this address against the employer’s legal name on the Labor Condition Application (LCA) confirms corporate identity and proper compliance reporting. A mismatched legal name or a residential worksite address often signals a shell company or inaccurate petition. Users must align the legal entity registered with USCIS against the actual street address, as multiple subsidiaries may share a parent brand but hold distinct legal names in the record.

Strategic Uses for Job Seekers and Recruiters

Job seekers can strategically use the H1B database to identify employers with a proven history of sponsoring visas, targeting their applications to companies actively hiring foreign talent. Recruiters can leverage the same data to source candidates currently on H1B status, facilitating seamless transfers without new filing caps. Cross-referencing job titles within the database allows both parties to pinpoint realistic salary benchmarks and role expectations for specific industries. A recruiter might filter by occupation code to build a pipeline of candidates from competitors, while a job seeker can verify whether a prospective employer has consistently sponsored roles matching their skill set.

Identifying Top Sponsoring Firms and Industry Trends

By querying the H1B database for employer EINs and petition volumes, job seekers can isolate high-volume sponsoring firms that consistently hire for specific roles. Analyzing year-over-year filing counts from this data reveals which industries have sustained recruitment demand, such as tech or consulting sectors showing steady petition growth. Cross-referencing job titles with company locations in the database identifies industry specialization hubs, allowing users to target firms with concentrated expertise. A simple frequency table of top sponsors by occupation code offers a direct comparison of employer hierarchy within a field.

Metric	Action for Identifying Sponsors
Petition Volume	Sort by highest counts to reveal dominant firms
Year-over-Year Change	Filter to see which industries expanded hiring
Job Title Clusters	Group to pinpoint niche sector sponsors

Benchmarking Salary Offers Against Public Filings

Job seekers can use the H1B database to benchmark salary offers against public filings by comparing a specific employer’s disclosed wage data for similar roles. This process provides a verifiable market floor, revealing whether a recruiter’s initial offer aligns with documented compensation levels for that company and location. Recruiters leverage this data to validate that their proposed salary is competitive relative to what competitors have actually paid for comparable positions, avoiding reliance on self-reported surveys.

• Filter H1B data by employer name and job title to extract exact salary figures from certified labor condition applications.
• Compare multiple years of an employer’s filings to identify consistent pay ranges versus outliers.
• Cross-reference geographic area codes within the database to ensure location-adjusted salary benchmarks.

Detecting High-Demand Occupations and Locations

Job seekers can pinpoint high-demand occupations and locations by analyzing H1B petition volumes across specific job titles and cities. Filtering for software developers in Seattle versus Chicago reveals clear hiring hotspots, while recruiters can isolate which firms filed the most visas for niche roles, like data engineers in Austin. A quick scan of employer concentration by metro area shows where competition for talent is fiercest, helping you target applications or sourcing efforts h1b data directly.

Data Point	Action for Job Seeker	Action for Recruiter
Top job titles by petition count	Identify which roles are getting mass sponsorship	Focus sourcing on these titles in high-petition cities
Employer locations with highest visa volume	Prioritize job applications to those metro areas	Map competitor hiring hubs for candidate outreach
Unique job-company-location combinations	Spot companies repeatedly hiring your skill set locally	Detect emerging demand clusters before market catches on

Legal and Privacy Considerations

Accessing an H1B database requires strict adherence to data protection laws. Users must verify that the platform lawfully sources records, as unauthorized scraping or redistribution of personal information—including names and compensation details—can violate privacy regulations. To mitigate liability, only use databases that explicitly anonymize or aggregate data and provide clear terms of service regarding permissible use. Additionally, remember that even legally obtained H1B data should not be used for discriminatory employment decisions. Practically, always check for a published privacy policy and respect any opt-out mechanisms for listed individuals. Ignoring these legal and privacy considerations exposes you to potential civil penalties and reputational harm.

What Information Is Legally For Public Viewing

When you dig into an H1B database, the info legally viewable includes the employer’s name, the job title, the offered wage, and the petitioner’s address. You can also see the application’s status and filing dates. However, personal details like the worker’s home address and private phone number are shielded by privacy laws. The database focuses on the job and employer, not the employee’s personal life. Anything that could identify an individual outside of work—like their social security number or family details—is legally excluded from public records.

Publicly Viewable	Not Publicly Viewable
Employer name & address	Worker’s home address
Job title & wage	Social security number
Application status	Private phone number

Limitations on Using the Data for Hiring Decisions

Using the H1B database for hiring can be tricky. You can’t assume a candidate’s visa status is current, as the data reflects past filings. There are also serious legal risks from discrimination claims if you filter candidates solely based on nationality or employer history. The data lacks context—like denied applications or green card sponsorships—so over-reliance leads to false conclusions. Stick to it as a starting point, not a final verdict.

• Never use nationality or employer origin as a hiring criterion; it invites liability.
• Validate any visa status before making an offer; filings can expire or change.
• Avoid making assumptions about job performance based on an employer’s past H1B usage.
• Don’t substitute the database for comprehensive candidate vetting processes.

Redaction Policies and Worker Identity Protections

Redaction policies within an H1B database govern which worker identifiers are masked before public disclosure to mitigate privacy risks. Typically, home addresses, phone numbers, and signatures are redacted, while the beneficiary’s name and employer remain visible for visa tracking. Worker identity protections rely on selective truncation of personal data fields, ensuring anonymity without negating transparency. Overly aggressive redaction can impede a worker’s ability to verify their own record for errors. A consistent policy must balance open access with safeguarding against targeted solicitation or identity theft.

Redacted Field	Protection Purpose
Home address	Prevents physical stalking or harassment
Social Security number	Blocks identity theft or wage manipulation

Analyzing Trends Through the Employer Filing Records

Analyzing trends through the employer filing records in the H1B database involves examining petition volumes, job titles, and salary levels across specific companies over time. By sorting employer records, you can identify which firms consistently sponsor visas for particular roles, such as software engineers or data scientists, and how their wage offers compare year-over-year. What can this reveal? For example, a decline in filings from a major tech company might indicate a shift in hiring strategy or internal restructuring, while a sudden increase from a smaller firm could signal new projects or expansion. This granular view helps job seekers target employers with stable sponsorship patterns or track competitor activity within an industry niche.

Year-Over-Year Changes in Visa Sponsorship Volumes

Analyzing year-over-year changes in visa sponsorship volumes within the H1B database reveals shifting employer demand and approval patterns. By comparing filing counts across consecutive fiscal years, users can identify which companies increased or decreased sponsorship reliance over time, often signaling strategic workforce adjustments. These annual comparisons isolate outliers, such as a sudden 40% drop in petitions from a previously consistent sponsor, helping job seekers calibrate application timing.

• Compare total LCA filings per employer for fiscal year 2023 versus 2024 to spot stable or erratic sponsors.
• Track year-over-year volume changes for specific job titles to see if roles are expanding or contracting.
• Measure the percentage change in approvals per employer annually, filtering out one-off spikes from sustainable trends.

Geographic Distribution of Approved Labor Applications

The geographic distribution of approved labor applications within the H1B database reveals exactly which states and cities are currently absorbing the most foreign talent. By filtering the records, you can see that areas like California, Texas, and New York consistently dominate, but smaller tech hubs are growing fast. This data is key for navigating regional job markets because it shows where companies are actively filing and winning approvals.

• Pinpoint which metro areas have the highest density of approved applications for networking.
• Compare coastal vs. inland locations to find less competitive filing zones.
• Use zip-code level data to target employers in specific local clusters.

Sector-Specific Growth Patterns in Skilled Worker Hires

The H1B database reveals distinct sector-specific growth patterns in skilled worker hires, showing tech and healthcare firms scaling visa requests year-over-year while manufacturing remains steady. You can filter employer filings by NAICS code to compare expansion in software development versus biomedical research roles. Some finance companies have shifted toward data science hires, whereas engineering sectors show cyclical spikes tied to project launches.

• Healthcare organizations now file more H1B petitions for machine learning specialists than for traditional clinicians.
• Cybersecurity firms in the financial sector display a 150% hire increase over three filing cycles.
• Renewable energy employers consistently add cloud infrastructure roles, not just engineering posts.

Tools and Methods for Data Extraction

From my first scrape of the USCIS public disclosure files, I learned that Python with BeautifulSoup remains the most reliable tool for parsing the semi-structured HTML tables of the H1B database, especially when handling the inconsistent employer names and wage fields. A more surgical approach involves using custom SQL queries against a local PostgreSQL mirror of the data, which lets you filter by SOC code or employer ID in milliseconds rather than waiting on the clunky government portal. I once spent a full day debugging a failed extraction, only to find the employer column had a hidden null-byte character that broke my CSV parser. For bulk downloads, I rely on wget with a recursive flag to grab all PDF-based LCA records, followed by tabula-py for table extraction—though it still chokes on merged cells.

Manual Searches Versus Automated Scraping Approaches

For the H1B database, manual searches through the Foreign Labor Certification Data Center offer precise, legally vetted records but become impractical for bulk analysis due to time constraints. In contrast, automated scraping using python scripts with BeautifulSoup or Selenium dramatically accelerates data collection, enabling extraction of thousands of employer-sponsor records in minutes. However, scraping carries risks of IP blocking and legal gray areas, whereas manual methods guarantee compliance. Automated scraping provides scale but requires technical upkeep; manual searches sacrifice speed for absolute safety. Your choice hinges on whether you need a few spot-checked cases or a comprehensive dataset for longitudinal analysis.

For the H1B database, manual searches ensure legal compliance but lack efficiency for large datasets, while automated scraping offers speed and scale at the cost of potential access restrictions and technical complexity.

Popular Third-Party Platforms That Repackage the Data

For a more user-friendly take on the h1b database, several popular third-party platforms repackage the raw government data into searchable dashboards. These sites extract filings from the DOL and display them through clean, filterable interfaces. To use them effectively, follow this simple sequence:

1. Visit a site like H1BGrader or H1B Salary Database and enter your employer or job title.
2. Set filters by year, location, or salary range to narrow the results.
3. Review the cleaned-up summary tables, which often include company approval rates and average pay.

Exporting Filtered Results Into Spreadsheets for Analysis

Exporting filtered results into spreadsheets transforms raw H1B database queries into actionable insights. Once you refine employer or wage data, initiate an export to download a structured CSV or Excel file. The process typically follows a clear sequence: spreadsheet-optimized data export to capture your filters.

1. Select your desired filters (e.g., employer, fiscal year).
2. Click the “Export” or “Download” button usually located near the results table.
3. Choose a file format like CSV or XLSX.
4. Open the file in your spreadsheet application to sort columns, apply conditional formatting, or run pivot tables directly on certified petitions without reconnecting to the database.

This method lets you compare salary percentiles and approval rates offline, turning site filters into a dynamic local analysis file.

Common Myths About the Public Worker Database

A common myth is that the H1B database reveals a worker’s current employer or job status. In reality, the Public Worker Database often lags by months, showing outdated applications that have been withdrawn or denied. Another misconception is that it tracks a person’s location; the database only lists the employer’s address on the approved petition, not where the worker actually lives. Many assume the database includes all H-1B employees, but it actually excludes renewals and certain visa categories, meaning the records are incomplete. People also think any name in the database proves illegal activity, yet the system simply logs legitimate filings, not violations. Finally, workers worry their private data is exposed, but the database omits personal details like salary breakdowns and home addresses, focusing solely on employer and job title.

Clarifying Misconceptions About Wage Accuracy

A common myth is that the H1B database displays an employee’s exact take-home pay. In reality, the wage figure represents the certified prevailing wage required by the Department of Labor, not actual salary. This prevailing wage is a minimum threshold, so actual compensation is almost always higher. Many users mistakenly assume the database shows real earnings, leading to false conclusions about underpayment. The listed wage only proves the employer met a legal floor, not the worker’s true negotiated pay.

Clarifying Misconceptions About Wage Accuracy: The H1B database shows a legal minimum prevailing wage, not the actual salary paid to the worker.

Why Not All Approved Petitions Result in Visas

An approved H-1B petition in the database does not guarantee a visa because approval only confirms the job and beneficiary meet legal requirements, while visa issuance depends on annual caps and consular processing. The annual visa cap limits mean that once the 65,000 regular cap (plus 20,000 for U.S. master’s holders) is reached, approved petitions are waitlisted for the next fiscal year, not automatically rejected. Additionally, an approved petition can be revoked if the employer withdraws sponsorship or the beneficiary’s status changes before the visa interview. The database reflects petitions, not visa stamps, so it may show approvals for individuals who never receive a visa due to cap exhaustion, administrative processing, or personal factors.

• Caps on H-1B visas create a lottery-like waitlist for approved petitions.
• Employer withdrawal or beneficiary status change can void an approved petition.
• Consular processing may deny a visa even after petition approval.
• Fiscal year timing determines if an approved petition leads to a visa.

Distinguishing Between LCA Filings and Visa Issuance

A common myth is that an LCA filing in the H1B database guarantees a visa. In reality, distinguishing between LCA filings and visa issuance is critical: the Labor Condition Application is an employer attestation to the Department of Labor, not a visa approval. H1B database entries reflect LCA certifications, which only prove wage and working condition compliance. Visa issuance is a separate, later step by USCIS and the State Department. An approved LCA provides no assurance of a final visa grant. The sequence is strict:

1. Employer files and receives LCA certification.
2. Employer submits H1B petition to USCIS.
3. USCIS approves or denies the petition.
4. Visa issuance follows only after petition approval.

What Is an H1B Database and Why Do You Need One?

Core Data Fields You Can Expect in Any H1B Database

Who Typically Benefits from Searching an H1B Database

Key Features to Look for When Selecting an H1B Database Tool

Search Filters That Save Time: Employer Name, Job Title, and Year

Export Options for Offline Analysis and Reporting

Real-Time Versus Snapshot Data: What Each Means for Your Results

How to Use an H1B Database to Find Past Visa Sponsors

Step-by-Step Guide to Running Your First Employer Search

Reading Wage and Job Category Entries Correctly

Common Mistakes Beginners Make with an H1B Database

Overlooking Case Status Filters and What They Indicate

Relying Solely on One Database Without Cross-Referencing

Misinterpreting Approved Versus Denied Petition Counts

Frequently Asked Questions About H1B Database Accuracy and Coverage

How Far Back Does a Typical H1B Database Archive Go

Can You Trust the Employer Names and Addresses Listed

Are Salary Figures in an H1B Database Adjusted for Inflation