- GS pay scale 2026
- Corrections
58 locality pay areasPage last changed 2026-10-07
Corrections to this site
Every correction to a figure or a statement that readers could see on the published site, with the day it was made. Newest first.
When something here turns out to be wrong, it is corrected on the page itself, the page’s “last changed” date moves, and the correction is listed below, and so is new data added to the pages. Changes to how the site is built or how it looks are not listed: only what a reader could have read and relied on. To report an error, write to hello@gspaytables.com with the page and the figure you expected.
Locality pages: Palm Bay, Burlington, Virginia Beach, Reno, Rochester, and those ranked by the swing of the pay gap between editions. The Palm Bay table gave 28.13 percent as the formula rate for pay in 2024, which is the Rest of U.S. target the memo assigned it, not a rate of its own. Burlington and Virginia Beach were listed as locality pay areas in the edition for pay in 2018, when the memo only recommended them. Reno and Rochester were said not to be listed in the editions for 2018 to 2022, which name them without a gap, and Reno, with four editions, was ranked by swing against areas with nine.
Now: Where a memo gives an area the Rest of U.S. target, Palm Bay and Corpus Christi alike, the table shows a dash and its caption says why; an edition that only recommends an area lists it as proposed; Reno and Rochester read “give it no gap”; swings are ranked among the 56 areas with a gap in all nine editions.
The 15 grade pages, /methodology/. The military grade table cited only Table 2 of DoD Instruction 1000.01, though the officer titles are from its Table 1 and the statement that the equivalence gives no rank or authority is from Enclosure 2, paragraph 4.b; the site’s own note that it is not a pay equivalence stood before the source and read as part of it. The table sat under the question about hourly pay.
Now: Each grade page answers “What military rank is GS-N equivalent to?” under its own heading, cites Tables 1 and 2 and paragraph 4.b, and adds its note after the source; the methodology page says what the instruction is for and what it does not cover.
/states/virginia/, /states/maryland/, /states/missouri/, /states/nevada/. The Virginia page called its 66 places on the Rest of U.S. rate “all other counties”; 16 of them are independent cities. These four state pages counted their independent cities as counties.
Now: The pages count counties and independent cities apart: in Virginia, 50 counties and 16 independent cities on the Rest of U.S. rate.
The 15 grade pages. The grade pages did not say which military grade a General Schedule grade corresponds to.
Now: Each gives the military grade, the warrant officer grades where there are any, the Geneva Conventions category and the officer titles that DoD Instruction 1000.01 sets beside it for identification cards, and says that this is not a pay equivalence.
The 38 state pages with more than one locality pay area. A state page gave each area’s pay and the number of the state’s counties it covers, but not which counties they are.
Now: Each lists the counties of the state in each area as OPM’s 2026 definitions give them, with the military installations OPM assigns, and the number of counties on the Rest of U.S. rate.
/compare/ and six former pair addresses; the Washington, DC, Los Angeles, New York, San Diego, San Jose and Houston locality pages. From 6 October the six former addresses that set an area against Rest of U.S. redirected to their pair on /compare/; search engines drop the part of an address after “#”, so for these searches they listed the top of /compare/ instead of the pair.
Now: They redirect to that area’s page, which now states the difference from Rest of U.S. at GS-12 step 5 and the price level at which the Rest of U.S. rate buys as much; the other fifteen pair addresses still lead to their pair on /compare/.
Nine locality pages (Birmingham, Corpus Christi, Des Moines, Fresno, Omaha, Reno, Rochester, San Antonio, Spokane). Each said that only some of the nine Federal Salary Council editions checked here include the area. The earlier editions list it in their research-area tables with a pay gap of its own, and Corpus Christi showed no formula rate in any edition.
Now: The table of editions shows those research-area gaps and says where the area is listed as what; the ranks of change and of swing between editions count them; Corpus Christi shows its own formula rate for pay in 2020 to 2022.
The 15 grade pages, /methodology/. Grade pages gave a median full-time “basic pay” without saying that OPM withholds the pay of 550,140 of the 1,279,389 General Schedule records, every Department of Defense record among them, and that the figure includes locality pay; GS-1 and GS-2 medians rested on 25 and 73 records.
Now: Each median says how many full-time employees it is taken from and what share of the grade that is, the label says locality pay is included, GS-1 and GS-2 carry no median, and the methodology page describes the withheld pay.
/how-locality-pay-works/, /locality/state-of-alaska/, /locality/state-of-hawaii/. Senate Report 110-456 was cited as the report on the law that replaced the Alaska and Hawaii cost-of-living allowance with locality pay.
Now: It is cited as the report on S. 3013, the 2008 bill that proposed the change; the change was enacted as sections 1911 to 1919 of Public Law 111-84.
/states/no-locality-area/, /how-locality-pay-works/. The pages said the list of locality pay areas is decided by the Federal Salary Council and the President.
Now: They say the President’s Pay Agent defines the areas (5 U.S.C. 5304(f)(1)) on the council’s recommendation.
/step-increase/. The page cited 5 CFR 532.417 for the Federal Wage System’s five steps and waits of 26, 78 and 104 weeks; that section refers to the law and does not state the waits.
Now: It cites 5 U.S.C. 5343(e), where the steps and the waits are set.
/law-enforcement/, /calculator/. The law enforcement page showed steps 1, 5 and 10 of the GL table only and no GL rate with locality pay, and the calculator worked out General Schedule rates only.
Now: The page shows all 80 GL rates with any area’s locality pay and a table of all 58 areas, checked against five of OPM’s published law enforcement tables; the calculator has a GL pay plan for grades 3 to 10.
The 58 locality pages, the 15 grade pages. Locality pages gave every rate a year only, and grade pages did not say what a grade pays an hour.
Now: Every locality page has the hourly and biweekly rate of all 150 cells (the annual rate divided by 2,087 hours, and that times 80), matching OPM’s hourly tables, and each grade page has an hourly column and answers whether the grade is a high one from OPM and BLS figures.
The 58 locality pages, /methodology/. Each locality page said the Federal Salary Council “has published a gap” for the area “in nine editions, the first for locality pay in 2018”. The council’s memos go back to 2003; nine is the number of editions this site has loaded.
Now: The pages speak of the editions checked here, the memos for pay in 2018 to 2026, and the methodology page says the memos go back to 2003 and that an area may appear in earlier ones.
The 58 locality pages, the 39 state pages, the 15 grade pages. The same paragraphs stood on every page of each kind with only the names and numbers changed: the same caveats under each table, a sentence on how the pay law’s formula has been set aside since 1994, and an example of a swinging estimate taken from one area (Laredo, TX) on every locality page.
Now: Each page carries its tables and only the sentences that single its own area or grade out, such as one of the five highest or lowest figures of a kind; how each source works and what it cannot show is on the methodology page, once, and the 1994 history on the pay raise page.
/. The home page had no General Schedule pay table: its first figure was the range of one cell, GS-12 step 5, across the areas.
Now: It opens with the full 2026 table, 15 grades by 10 steps, as base rates, with any area’s rates a choice away, the 2027 status from the pay raise tracker, and links to OPM’s official tables.
/states/no-locality-area/. The page advised checking whether a border county belongs to an area named after a city in the next state, although in OPM’s 2026 definitions no county of these eight states is in a named area.
Now: It says that no county of these states is on any named area’s county list and that no installation in them is assigned to one.
/how-locality-pay-works/. The page said the area that pays more runs into the ceiling first and that “over a career that can matter more than the difference in any single year”, as if the ceiling touched most careers.
Now: It says where the ceiling binds: 97 of the 8,700 cells, at the top of GS-15 and GS-14, in 37 of the 58 areas.
/contact/. The contact page asked anyone who wanted to quote or reproduce the site to write for permission, while the terms license the same text CC BY 4.0.
Now: It points to the CC BY 4.0 license in the terms: reuse with attribution and a link, no permission needed.
/pay-raise/, the 58 locality pages, the 15 grade pages. The pay raise page gave the 2027 status in prose with the 2027 base table as proposed, and the locality and grade pages said only that their rates hold until January.
Now: The pay raise page tracks each step of the 2027 decision with its date, status and primary source, works out three scenarios (the proposed freeze, the FAIR Act, H.R. 7480 and S. 3823, and the statutory formula), lists every locality pay area's 2027 rate as proposed, sets a freeze against the latest consumer prices area by area, and gives the 2027 law enforcement plan and paycheck dates. Each locality and grade page states its own 2027 figure under the proposal.
The 58 locality pages, the 39 state pages, /step-increase/ (new), /methodology/. The locality and state pages gave the 2026 rates and prices only, and the site had no way to work out when a step increase is due.
Now: Each locality page adds its locality pay from 2016 to 2026 from OPM's table for each year, the rate the 1990 pay law's formula would set there by the Federal Salary Council's latest estimate, and its federal jobs from the Bureau of Labor Statistics; each state page adds its federal jobs area by area; /step-increase/ dates the next step increase. What each source can and cannot tell is on the methodology page.
/compare/ and the 21 pair pages it replaced; the Alaska, Delaware, District of Columbia, Hawaii and Rhode Island pages. Twenty-one pages each compared one fixed pair of areas, and five states covered entirely by one locality pay area each had a state page that repeated that area’s page.
Now: The comparison tool on /compare/ sets any two of the 58 areas side by side, and each former pair address redirects to that pair on it (from 7 October the six pairs of an area against Rest of U.S. redirect to that area’s page instead, see that day); the five state addresses redirect to the page of their locality pay area, which names the state. The 14 promotion pages had been folded into /promotion/ the same way on 1 October.
/states/no-locality-area/. The page said the number of locality pay areas had grown “from 48 to 54 to 58”, the same figures corrected on the methodology page the same day.
Now: It gives OPM's counts: tables for 47 areas in 2016, 53 in 2019, 54 in 2021 and 58 from 2024.
/law-enforcement/. Law enforcement availability pay (LEAP) was computed as 25 percent of the base rate: $15,000 a year at GL-10 step 1.
Now: Under 5 CFR 550.185 and 550.103 it is 25 percent of the rate of basic pay, which includes the locality payment: $20,091 at GL-10 step 1 in Washington-Baltimore, where OPM's table 2026-DCB (LEO) gives $80,363. The build now checks the page against that OPM table. The worked example also set a Washington-Baltimore GL-7 salary against the GS-7 base rate before locality pay; it now compares it with the GS-7 salary in the same area.
/law-enforcement/, /calculator/, /methodology/. Three pages contradicted each other about law enforcement pay. The law enforcement page said the calculator adds locality pay to the GL rates; the calculator page said law enforcement officers are “entitled to higher locality rates”; the methodology said the site does not “cover … law enforcement officer rates”.
Now: The calculator uses the ordinary General Schedule table and says so. Law enforcement officers at grades 3 to 10 have a higher base table with the same locality percentage as everyone else in their area, and positions covered by the 2026 special rates are paid the special rate where it is higher. Both are set out on the law enforcement page.
/law-enforcement/, /pay-raise/, /grades/, /calculator/, /states/. The law enforcement page described 2026 pay by the GL table alone and said “Above grade 10 the special rates end”. Since 11 January 2026 positions covered by OPM's law enforcement special rates (memo CPM 2025-25) are paid from tables L001 to L133, which cover every grade; in Washington-Baltimore table L058 puts GL-7 step 1 at $67,248, not the $65,435 the page gave. The pay raise page said the proposed 3.8 percent for 2027 comes “on the separate GL base table”.
Now: The page explains both tables with OPM's figures and links. The 2027 increase is to be paid through OPM special salary rates under 5 U.S.C. 5305, with coverage to be announced with the tables; the GL base table moves with the General Schedule base.
/pay-raise/. The page said the base pay formula “has been set aside every year since 1994” and that “every President has used that power every year since 1994”. It gave the window for the December executive order as 18 to 23 December, from four years of history. It said the 2027 budget request “contains no pay raise for civilian federal employees”, which could not be found in the budget itself, and described the FAIR Act's locality figure as about 1 percent.
Now: For 2020 the base increase followed the formula (2.6 percent, House Document 116-59); what has not been followed since 1994 is the locality formula, overridden by Congress or by the President. The page adds the 2020 precedent (Public Law 116-93, Executive Order 13901 on 26 December 2019), and seven years of history give a window of 18 to 31 December. The budget is cited only for what the President's letter says of it, and the FAIR Act's locality adjustment is given as the bill states it: 1 percent.
/how-locality-pay-works/, /calculator/, /methodology/, the 21 comparison pages. The overtime cap was described without its scope, comparison pages said time and a half “stops at the hourly rate of GS-10 step 1”, and they said the GS-12 overtime hour “still carries a genuine premium”. How locality pay works said the premium “disappears sooner in a better-paid area”.
Now: The cap is the Title 5 rule (5 U.S.C. 5542, 5 CFR 550.113) as it applies to employees exempt from the Fair Labor Standards Act; an employee covered by the FLSA is paid under whichever rule gives more (5 CFR 551.513). Above GS-10 step 1 the overtime hour is capped at one and a half times the GS-10 step 1 hourly rate, and at GS-12 step 5 that is about half a percent above the ordinary hourly rate, as the comparison tool now computes. Locality pay scales the threshold and the employee's rate alike, so the premium ends at the same cell, GS-12 step 6, in all 58 areas.
/pay-raise/. The page title read “2027 Federal Pay Raise: Frozen at 2026 Rates”, stating a proposal as a fact. The earlier pay freeze was dated 2011 and 2012. Locality payments in 2026 were said to have risen “by exactly 1.0 percent and not a cent more”. The top of the page showed two different dates.
Now: The title says the freeze is proposed. The freeze covered 2011, 2012 and 2013: OPM's tables for all three years are headed “Rates frozen at 2010 levels”. The 1.0 percent is stated as a percentage, with rounding to the dollar and the ceiling named. One date at the top: the day the page last changed; the status check date is stated with the sources.
Every page. The footer and the structured data of every page gave the date the OPM and BEA data last changed (18 September 2026), including on pages corrected on 1 October, while the sitemap gave a different date.
Now: Each page shows the date its own content last changed, and the footer, the structured data and the sitemap carry that same date.
The home page, the 58 locality pages, /calculator/, /states/, /law-enforcement/, /about/. Several pages claimed of the purchasing-power comparison that “nobody else publishes this” or that it is “the one thing no other reference site publishes”. The claim had never been checked against every other site and could not be supported. The grade pages, the grades index and the calculator said of the base table “Nobody is actually paid this”; General Schedule employees stationed outside the United States receive no locality payment. The About page said the price index lags the pay tables by about two years while other pages said a year or more.
Now: The claims are gone; the pages say what the official tables do not show, which can be checked, and that no duty station in the United States pays the base rates as they stand. The price-index lag is one computed statement on every page that mentions it.
/methodology/. The methodology said the number of locality pay areas had changed “from 48 to 54 to 58”.
Now: OPM's yearly index pages list tables for 47 areas in 2016, 53 in 2019, 54 in 2021 and 58 from 2024; the page now gives those counts.
/promotion/ (then 14 separate promotion pages), the grade pages. Promotions from step 9 or step 10 were worked out as if the two step increases of the two-step rule could not go past step 10: GS-12 step 10 to GS-13 was shown as $614 more in base pay. Every pair was also said to need 52 weeks in grade, and a grade page said a promotion from GS-11 is worth about $14,356 (step 5 to step 5).
Now: Above step 10 the two step increases are added in dollars, as in OPM's own promotion examples (5 CFR 531.214): GS-12 step 10 to GS-13 is $6,676 more in base pay. Below GS-5 there is no time-in-grade minimum (5 CFR 300.604). GS-11 step 5 to GS-12 is worth $6,709 by the rule.
17 state pages. Seventeen state pages described the whole state as one locality pay area and left out the Rest of U.S. rate that applies to counties outside every named area. Tennessee was shown as entirely inside the Huntsville area, which covers one of its 95 counties.
Now: Rest of U.S. is a row on every state page where it applies, and the pay spreads quoted for those states changed with it.
Locality, state, comparison and grade pages; /methodology/. The Alaska and Hawaii pages carried text written for Rest of U.S. Forty locality pages said the steps of a grade are not evenly spaced, which is true only of GS-1 and GS-2. Negative differences were printed with the minus sign after the dollar sign on five comparison pages and nineteen state pages. The methodology said twenty-nine checks stop publication when there were forty.
Now: Each of these now says what the data shows; the number of checks on the methodology page is taken from the build itself.
/pay-raise/. The page said there was no published figure for what full locality pay would cost in 2027 and quoted the 2026 letter instead. It also said the build refuses to publish once the status check is older than 40 days.
Now: The 2027 letter (House Document 119-189) gives the figure: an average locality increase of 20.6 percent costing $26 billion in the first year. After 40 days the build warns; it refuses to publish when a date in the calendar of this subject has passed since the last check.
/privacy/, /terms/. On the day Google's advertising code was added to every page, the privacy page still said the only outside requests went to Google Analytics and that the site carried no advertising.
Now: Corrected the same day. The list of outside services is built from the same settings that load them, so the two cannot drift apart.
The 58 locality pages, /methodology/. The methodology said the metropolitan area used for each locality's prices is named; it was not named on any page. It also said sixteen checks stop publication (there were twenty-nine) and that 920 counties lie in 57 areas (they lie in 55).
Now: Each locality page names the metropolitan area its price level was measured for, and the methodology states both counts as they are.
The 58 locality pages, the home page, the calculator. Six locality pay areas were priced with another place's price index, three of them in another state: St. Louis with Farmington, NM; Columbus, OH with Columbus, GA-AL; Rochester, NY with Rochester, MN; Atlanta with Athens-Clarke County, GA; Cleveland with Akron, OH; Huntsville with Decatur, AL.
Now: Each area is matched to its own metropolitan area. 39 of the 57 purchasing-power ranks changed, by up to 30 places.
/pay-raise/, the 15 grade pages. For fifteen days after the President's 26 August letter proposing a freeze, the pay raise page said the 2027 raise had not been decided. The search descriptions of the grade pages gave the step 5 range as the range of the whole grade: GS-14 “$142,549 to $178,204”.
Now: The page leads with the proposed freeze. The grade range runs from step 1 in the lowest-paying area to step 10 in the highest-paying one: $125,776 to $197,200 for GS-14.
The 15 promotion pages. A stray line-break code was printed as two visible characters before every heading.
Now: Removed, and the build now refuses to publish visible escape characters.