HUD FMR history: how fair market rent methodology changed
The short answer
A Fair Market Rent published in FY2026 looks different from one published in 2000, and the difference comes from three deliberate changes rather than drift. First, the percentile moved: FMRs sat at the 50th percentile of gross rent until FY2000, and the Quality Housing and Work Responsibility Act of 1998 reset the standard to the 40th percentile starting with the FY2001 numbers. Second, the geography thickened: one rent per metro area is still the default, but since FY2018 many metros run on ZIP-level Small Area FMRs. Third, the machinery underneath was rebuilt repeatedly, and those rebuilds are why an area's number can jump between fiscal years even when its rents barely moved.
Anyone reading FMR history should hold one number in mind as the current endpoint: the FY2026 2BR median across all 51,895 ZIP rows is 1,150 dollars a month. Every rule below produced that file.
From 50th to 40th percentile, FY2001
Through the 2000 FMRs, HUD set each area's number at the 50th percentile of gross rent, the middle of the local distribution. The Quality Housing and Work Responsibility Act of 1998 (Public Law 105-276) rewrote the standard to the 40th percentile, and HUD first applied it to the fiscal year 2001 FMRs, where it has stayed ever since.
The percentile switch moved the whole series down by construction: 40 percent of standard units rent below the FMR, instead of half. HUD still publishes 50th percentile rent estimates as a separate product on huduser.gov, so an old-looking high number may be that product rather than a past FMR. The current standard, 40th percentile gross rent, shelter rent plus utilities, applies to metro-wide FMRs and to Small Area FMRs alike.
From one number per metro to one per ZIP
The second change is geographic. A metro-wide FMR gives every ZIP in the area the same ceiling, which concentrates voucher use in low-rent neighborhoods and falls short in high-rent ones. HUD tested the ZIP-level fix with a demonstration that started in Dallas in 2012, proposed a rule in June 2016, and finalized it that November (81 FR 80673). Since fiscal year 2018, HUD has designated metro areas each year where housing agencies must base payment standards on the ZIP-level SAFMRs.
Each SAFMR is the same 40th percentile gross rent estimate, computed at ZIP scale from American Community Survey five-year data plus private rent data on recent moves. The result is a file where geography carries more information each year: ZIPs in a designated metro get their own values, and the rest inherit their metro's number. SAFMR vs FMR covers the designation mechanics, and HUD payment standard shows the band arithmetic the ZIP values feed into.
Why FMRs jump between fiscal years
Year-over-year moves mix two causes: the rental market, and HUD's methodology. A methodology change can shift an area's number with no market movement at all. The known causes:
- New survey base. Each FMR grows out of a multi-year American Community Survey file collected before the release, re-priced to the fiscal year with an inflation adjustment. A new base file changes the distribution the percentile is cut from.
- Recent-mover tuning. HUD tunes the estimate toward what recent movers pay. Adjustments to that weighting move the number independently of standing tenants' rents.
- Area redefinitions. HUD area boundaries follow OMB metro definitions. When a county or ZIP is reassigned between HUD areas, its FMR changes with it, sometimes sharply.
- Minimum-rent floors. Low-rent areas fall back to state or national minimums, and parts of Texas do this in FY2026. An area crossing into or out of a floor sees a step change.
- SAFMR rollout. A ZIP picked up by a SAFMR designation swaps its metro-wide value for its own, a one-time move in either direction.
- The percentile switch itself. FY2001 dropped areas from the 50th to the 40th percentile, the largest one-time methodology move in the series.
The practical habit: before reading a year-over-year change as market news, read HUD's methodology notes for both fiscal years on the FMR documentation page. Where two numbers disagree, one of them may describe a different survey base, geography, or percentile, and the notes say which.
What the FY2026 file can and cannot show
The HUD FMR FY2026 pack carries 51,895 ZIP rows, 3,229 county rows, and a 52-row state summary, all FY2026. It has no historical columns and no SAFMR flag column; the schema is zip, hud_area_code, metro, area_name, state, and fmr_0br through fmr_4br. That means the pack anchors one point of the time series rather than the series itself. Past fiscal years stay in HUD's published archive on huduser.gov.
What one year does show is the geography the history produced. In the free 22-row sample from Abilene, TX MSA, 12 of 22 ZIPs sit at the metro-wide base 2BR value of 1,090, and 10 carry higher values of their own, up to 1,900 in ZIP 79562, 810 dollars above the base:
| zip | hud_area_code | fmr_2br | vs metro base |
|---|---|---|---|
| 76437 | METRO10180M10180 | 1090 | base |
| 79508 | METRO10180M10180 | 1240 | +150 |
| 79536 | METRO10180M10180 | 1460 | +370 |
| 79562 | METRO10180M10180 | 1900 | +810 |
One hud_area_code, four values for the same bedroom count. That spread is the ZIP-level expansion rendered as data, though the file itself does not label which rows are SAFMRs; rows that differ from the metro base are a hint, and HUD's SAFMR tables carry the official designation. At the other end of the scale, the state summary condenses the country to 52 rows, and the FY2026 2BR median across all ZIP rows comes out at 1,150.
For a time series built from the pack, compare like with like: same hud_area_code, same percentile, and ZIP rows checked against the SAFMR tables for both years. HUD fair market rent data, explained covers every column, and FMR vs actual rent shows how the benchmark sits against asking rents.
FMR history questions
- When did HUD FMRs move to the 40th percentile?
- Through fiscal year 2000, HUD set FMRs at the 50th percentile of gross rent. The Quality Housing and Work Responsibility Act of 1998 (Public Law 105-276) changed the standard to the 40th percentile, and HUD first applied it to the fiscal year 2001 FMRs. The 40th percentile has held through FY2026, and it applies to Small Area FMRs as well as metro-wide ones.
- Does the FY2026 pack include FMRs from past years?
- No. The pack carries FY2026 only: 51,895 ZIP rows, 3,229 county rows, and a 52-row state summary. For a time series, HUD's FMR archive on huduser.gov keeps the published tables for past fiscal years. What the FY2026 file does show is geography inside one year: ZIP rows that differ from their metro's base value, which is where Small Area FMRs and other area rules live.
- Why did an area's FMR jump from one fiscal year to the next?
- Some of the move is the market, and some is methodology. Methodology causes include a new ACS base file, inflation adjustment, changes to recent-mover weighting, OMB metro redefinitions that move a ZIP or county between HUD areas, minimum-rent floors that catch low-rent areas, and a ZIP picking up a SAFMR instead of its metro value. Each of those can shift a number even when local rents barely moved, so a year-over-year comparison should start with HUD's methodology notes for both years.
Get the data
Start with the free 22-row sample to check the schema, then take the full pack when it fits. The full pack carries all three CSVs (51,895 + 3,229 + 52 rows), the data dictionary, and source checksums.
Checkout and download run through Getly. Source: US Department of Housing and Urban Development, FY2026 Fair Market Rent release, huduser.gov. US government data, public domain. Data Vault is not affiliated with HUD.