11 min read
Short answer: You shouldn't put your street address on a US resume in 2026. Employers don't need it to screen you, parsers often trip on multi-line mailing blocks, and zip codes can trigger bias you'll never see. Use email and phone. Add city and state on one line only when the role has a real location filter you want to match.
You're not crazy if you've stared at the header wondering what recruiters still expect. Most corporate reqs run through Workday or Greenhouse, and those systems care about job titles and dates long before they care which block you live on. Before you rebuild the file again, check your resume for free and confirm the contact block parses as contact, not as part of your name.
Below: why the street line died, when city/state still moves you through relocation filters, the exceptions that actually matter, and a copy-paste header you can drop in tonight.
Quick Wins
- Delete street, apartment, and zip from the resume header.
- Keep city and state on one line only when the posting names a location.
- Use Remote on fully remote reqs with no hub city named.
- Paste-test the header into Notepad before every upload.
Why US employers stopped asking for street address
Twenty years ago, recruiters mailed rejection letters. Today they email calendar invites. The resume header became a contact strip, not a mailing label. HR still collects legal address later on the application form, the offer packet, or the background vendor site. Putting it on page one duplicates data and opens privacy you don't need at the first screen.
Parsers read top to bottom. When your header spans four lines with street, unit number, city, state, and zip, Workday often grabs the wrong chunk as your name or shoves your first job title down the file. That's not a formatting quirk. That's a blank experience tab while your PDF thumbnail still looks fine.
City and state sit in a gray zone. They're not useless. Recruiters filter on metro for onsite roles, relocation budgets, and hybrid office days. But they don't help parsing the way a clean single-line phone number does. You're trading a relocation signal for another line the parser might misread. That's the trade most guides skip.
Screening reality: I've screened stacks of these in Workday and Greenhouse, and the file that wins is boring and specific. A three-line address block at the top is never the reason someone gets a callback.
Job searching is hard enough without guessing whether silence means "not qualified" or "parser thought your apartment number was your middle name." You deserve a header that gets out of the way.
Read why your resume never reaches a human for what happens after contact data parses wrong. This page stops you earlier, at the header layer where street lines still show up on templates from 2008.
Compare with DOCX export settings that improve US ATS parsing if your file looks clean visually but breaks on upload. Address clutter and export settings often fail together.
What to put in your resume header instead
Run these five checks on the contact block before you submit. Order matters when you're applying tonight.
Step 1: Strip street, unit, and zip
Open your master resume. Delete the mailing lines. Keep your name, one phone number with area code, professional email, and LinkedIn URL if you use it. That's the default US header in 2026. Background checks and payroll collect street data after you're in process, not from the PDF a recruiter skims in six seconds.
Before: Four-line block with 742 Oak Lane, Apt 12B, Portland, OR 97201 above your email.
After: Alex Rivera | [email protected] | (503) 555-0142 | linkedin.com/in/arivera-dev
Step 2: Decide if city and state earn a line
Read the posting. If it names Dallas onsite, a Dallas filter helps you. If it says remote US with no hub, Remote beats a random city. If you're relocating and the posting mentions relocation assistance, add Open to relocation on the same line as a target metro, not a fake current address.
Before: A Denver-based data analyst applying to Chicago onsite with no location line, then wondering why the req never surfaced.
After: Chicago, IL | Open to relocation on one line under the name, honest and filter-friendly.
Step 3: Format location on one line
Never stack city, state, and zip on separate lines. Use City, ST or Remote | US. Same font size as phone. No icons, no tab columns, no text boxes in the header. Parsers treat the first inch of the file as sacred ground. Waste it on address lines and your first bullet moves down the read order.
Step 4: Match the application portal
Many Workday forms ask for address in a dedicated field after upload. That's where street data belongs. Don't paste your old mailing block into the resume because the portal has a blank. Recruiters compare portal location to resume location when both exist. Mismatches raise questions you don't need at screen one.
Step 5: Paste-test before upload
Select the header, copy, paste into Notepad. Name, phone, and email should appear in reading order with no stray line breaks mid-phone-number. If your city landed above your name, rebuild the header in Word with simple left alignment. Re-export a text-based PDF and upload again.
Copy-paste: header templates by scenario
Local onsite role:
Jordan Lee
Austin, TX | [email protected] | (512) 555-0198
Fully remote, no hub named:
Priya Nair
Remote | US | [email protected] | (617) 555-0133
Relocating to target metro:
Marcus Cole
Seattle, WA | Open to relocation | [email protected] | (206) 555-0177
Hybrid with stated office days:
Elena Vasquez
Chicago, IL (hybrid) | [email protected] | (312) 555-0165
Composite: warehouse supervisor, local filter
Before: Full street address in header; recruiter's onsite filter for Phoenix metro never matched because zip parsed into the skills block.
After: Phoenix, AZ on one line; first bullet leads with OSHA 30 and 12% dock efficiency gain.
Composite: software engineer, remote req
Before: Suburban street address on a nationwide remote posting; hiring manager assumed long commute to optional quarterly onsite.
After: Remote | US header; cover letter notes willingness to travel quarterly when the posting mentions it.
Edge case: employer asks for address on the posting
Some government or clearance reqs mention residency in the job ad. Put city and state on the resume if it helps the filter. Still skip street until the formal application requests it. If the portal requires full address, fill the portal field and keep the resume header lean.
Edge case: you're staying private during a confidential search
Omit city and state when you're employed and the search is quiet. Use email and phone only. Mention relocation willingness in a recruiter call, not on a document that might circulate internally. You can add location back once you're public in the market. If the posting asks for a letter, generate a cover letter that states relocation interest without printing your home address on either file.
When city/state backfires on address decisions
Skipping street address is the easy part. These exceptions still waste good candidates when they follow outdated advice.
Exception: listing a city you don't live in. Metro filters help when you're honest. Faking Chicago while you're in Miami breaks trust the moment someone checks the portal or schedules a same-week onsite. Use Open to relocation instead of a false current city.
Exception: zip code in the header. Zip narrows neighborhood in ways city doesn't, and parsers love to glue five digits to your phone number. Drop zip from the resume entirely.
Exception: international address formats. Applying to US roles from abroad? Country line is fine when relevant. Street abroad in US-style headers confuses parsers and recruiters who expect a US metro or Remote. Put work authorization in the portal, not a foreign mailing block on line two.
Exception: two homes, two cities. Snowbirds and dual-residency candidates sometimes list both. Pick the city that matches where you'll work and pay taxes, or use Remote if the role allows. Splitting attention across two metros reads indecisive in a six-second skim.
Trusting the template default. Resume builders still ship with address fields because the software is old, not because recruiters asked for them. Blank the field on purpose.
Repeating address in summary and header. Once is enough. Twice eats lines you need for proof points.
Build a clean header before the next apply
Header fixes only matter when the rest of the file is worth sending. A lean address block with weak bullets still loses after you parse. A strong resume with a four-line mailing label still dies at upload. Check both layers.
Run a free ATS resume check with the job description pasted. Confirm contact lines parse separately from your name. Then build your resume in a single-column layout with the header templates above so you're not fighting a legacy template that insists on street address.
Your header tonight
So should you include address on a resume in 2026? Not your street. Not your zip. Maybe city and state on one line when the posting has a real location filter. Maybe Remote when it doesn't. That's the whole decision, and it's smaller than most template defaults pretend.
Open your file. Delete the mailing block. Paste-test the header. Match the portal when it asks for legal address later. Stop giving parsers four lines of contact clutter before your first proof bullet.
This won't fix applying to roles you're not qualified for. It stops a qualified file from dying because the parser read your apartment number as your job title. That's worth ten minutes before every batch of applications.
Read more
Frequently asked questions
No. US employers do not need your street address to schedule an interview or run a background check later in the process. A full mailing address adds privacy risk, can confuse parsers when it spans multiple lines, and rarely changes whether you get screened in. Use email and phone in the header. Add city and state only when the role has a location filter you want to match.
List city and state when the posting names an onsite or hybrid location, when you are open to relocation and want recruiters to see it, or when you are applying locally and commute distance matters to the hiring team. Skip location entirely on fully remote roles where the posting says anywhere in the US. Use one line, same font as your phone number, not a multi-line block.
Omitting street address usually helps parsing because parsers grab the first lines as contact data. A three-line address block often gets read as part of your name or pushes job titles down the file. City and state on one line parse fine in Workday and Greenhouse when formatted simply. Run a paste test into Notepad before you upload.
Use Remote, or Remote | US, when the posting is nationwide remote and you want zero location signal. If the employer lists a hub city for tax or payroll, match that metro only when you genuinely live there or plan to relocate. Do not fake a city to pass a filter. Recruiters verify location in the application portal anyway.
After you advance, HR collects legal address on the application form, offer paperwork, or background check vendor portal. The resume is a marketing document, not a payroll record. Keeping street data off the first screen reduces bias risk and keeps the header clean for parsers and humans alike.