Methodology and sources
How our construction calculators get their numbers
Every span, stair and guard limit on this site is read from a published code table: IRC 2021 for joists, rafters, headers, deck framing, stairs and guards, and AWC DCA 6-2015 for deck footing sizes. Inputs that fall between table values snap up to the next listed value, nothing is interpolated, and a result past the end of a table says so instead of guessing. This page lists each table, the page it came from, how it was checked, and the few cells where the published code itself is wrong.
IRC 2021 span tables and code sections behind each calculator
Each structural calculator reads one set of tables. The citation printed under every result matches a row here, so you can open the same page of the code and check the number yourself.
| Calculator | Source table | Loads and deflection | Source document and pages | How it was checked |
|---|---|---|---|---|
| Floor joist span | IRC 2021 Tables R502.3.1(1) and R502.3.1(2) | 30 or 40 psf live, 10 or 20 psf dead, L/360 | Seattle Residential Code Ch. 5, pp. 5-10 to 5-11 | All 1,024 values compared with the PDF text, 0 mismatches, plus a screenshot sample |
| Ceiling joist span | IRC 2021 Tables R802.5.1(1) and R802.5.1(2) | 10 or 20 psf live (uninhabitable attics), L/240 | Ch. 8, pp. 8-21 to 8-24 | 18-value screenshot sample, 18 of 18; the two tables cross-checked where they must agree |
| Rafter span | IRC 2021 Tables R802.4.1(1) to R802.4.1(8) | 20 psf roof live or 30, 50, 70 psf ground snow; 10 or 20 psf dead; L/180 or L/240 | Ch. 8 | 8 misprinted cells documented: 7 corrected from their sister table, 1 withheld |
| Deck joist span | IRC 2021 Table R507.6 | 40 psf live or 50, 60, 70 psf ground snow; 10 psf dead | Ch. 5, pp. 5-43 to 5-44 (original IRC text) | 18 spans and 2 cantilever values checked on screenshots, and a second independent entry matched 18 of 18 |
| Deck beam span | IRC 2021 Tables R507.5(1) to R507.5(4), factors from R507.5(5) | 40 psf live or 50, 60, 70 psf ground snow; 10 psf dead | Ch. 5, pp. 5-35 to 5-39 (original IRC text) | 18-value screenshot sample; one misprinted row withheld |
| Header size and beam span | IRC 2021 Tables R602.7(1) to R602.7(3) | Exterior and interior bearing walls by ground snow load and building width; open porches | Ch. 6, pp. 6-15 to 6-18 | 18 spans and jack stud counts checked on screenshots, 18 of 18 |
| Deck post size | IRC 2021 Table R507.4 | Post height by post size and tributary area | Ch. 5, pp. 5-32 to 5-33 (original IRC text) | 18-value screenshot spot check, 18 of 18 |
| Deck footing size | AWC DCA 6-2015 Table 4, p. 12 | Deck footing sizes | AWC DCA 6-2015 deck guide | Read from the published guide |
| Stair stringer and baluster spacing | IRC 2021 R311.7 (stairways) and R312.1 (guards) | Riser, tread, nosing, width, headroom, handrail, guard height and openings | Ch. 3, pp. 3-51 to 3-54 | Every limit checked against page screenshots |
| ADA ramp slope | 2010 ADA Standards for Accessible Design, Section 405 | 1:12 running slope, 30 in rise per run, landings | ADA Standards (federal, not the IRC) | Private houses fall under IRC R311.8.1 instead: 1:12 at the required egress door, 1:8 elsewhere (p. 3-54) |
Why the IRC is read from the Seattle Residential Code PDFs
The City of Seattle publishes its adopted residential code as free chapter PDFs, and those chapters reproduce the 2021 IRC text word for word, with Seattle's own changes marked. That makes them a public, citable copy of the model code that anyone can open and check.
Seattle marks its amendments with [W] and shows the IRC wording it replaced in double parentheses, struck through. Every table on this site uses the original IRC wording and ignores the Seattle change. Deck loads show why this matters: Seattle's Table R301.5 raises the deck live load from 40 to 60 psf, while the IRC deck tables here stay at 40 psf. If your jurisdiction amends a table the same way, its number is the one your inspector will use.
Source PDFs: Chapter 5 (floors and decks) · Chapter 3 (stairs and guards) · Chapter 8 (roofs and ceilings) · Chapter 6 (headers) from the same Seattle code set.
Blank cells, misprinted cells and results outside the table
A result can differ from a plain table lookup in three ways, and the calculator tells you which one applies.
Outside the table: the span, load or spacing is past what the IRC prints, or the table marks the cell as not permitted. That does not make the span impossible, only outside prescriptive code. Try closer spacing, a higher grade, a deeper member or an extra support to shorten the span, or take it to an engineer.
Misprinted and corrected: eight cells in the published 2021 rafter tables are wrong. Seven can be recovered, because where a span is limited by strength rather than deflection the same cell appears in the sister table with the stricter deflection limit. For those seven the calculator shows the corrected value and says so on the result, with the printed figure underneath.
| Table and cell | Printed in the IRC | What the calculator shows |
|---|---|---|
| R802.4.1(5): Hem-fir No.1 2x4 at 24 in, 50 psf snow, 20 psf dead | 8 ft 4 in | 5 ft 4 in, from R802.4.1(6) |
| R802.4.1(5): Spruce-pine-fir SS 2x10 at 16 in, 50 psf snow, 20 psf dead | 15 ft 11 in | 16 ft 8 in, from R802.4.1(6) |
| R802.4.1(1): Douglas fir-larch No.3 2x8 at 16 in, 20 psf roof live, 20 psf dead | 12 ft 12 in | 12 ft 2 in, from R802.4.1(2) |
Misprinted and withheld: two cells cannot be recovered from the code text, so no value is shown. One is a rafter cell printed as 1 ft 11 in. The other is the 1-2x12 deck beam row for Douglas fir-larch, hem-fir and spruce-pine-fir at the 16 and 18 ft columns, which repeats the 2x10 row above it. The full list is in the rafter table misprints post.
Rounding: every table input snaps up, nothing is interpolated
When your input falls between two values printed in a table, the calculator moves to the next value in the conservative direction and reads that column. It never estimates a number between two columns, and it never extends a table past its last column.
A worked example. IRC Table R602.7(1) lists header spans for buildings 12, 24 and 36 feet wide. For a 28 ft wide house the header calculator reads the 36 ft column, which gives shorter allowed spans than a 28 ft house strictly needs. Footnote c of that table permits interpolating between widths, so a designer could justify a slightly longer header. The tool does not, because a result you can check against one printed cell is worth more than a few extra inches.
The same rule runs through the deck beam table: the cantilever ratio and the effective joist span both move up to the next printed column. Deck joist cantilevers are the one exception: the backspan must match a printed value exactly, because those values do not rise in a straight line.
How each span table was checked before it went live
Every value is entered from the PDF and then checked against it. The floor joist table was compared cell by cell with the PDF text, all 1,024 values. The other tables were checked on a random sample of page screenshots, and the sample size is listed for each one in the table above.
Automated checks run on top: gaps, values that go the wrong way, and sister tables that must agree. The 10 psf ceiling joist table at 24 in spacing and the 20 psf table at 12 in spacing put the same load on each joist, so 64 of their cells have to match, and they do. A table only goes live once a person has marked it verified against the screenshots; the calculator refuses to load a table that has not been marked. Footnotes that change an answer, such as a longer end bearing for one floor joist size, appear only on the results they apply to.
How the quantity and geometry calculators work
The concrete, roofing and materials calculators are arithmetic, not code lookups, so the rules here are about keeping the arithmetic honest.
- Waste is added only to what you buy: bags, bundles, sheets, boards. Measured facts such as an area, a hole volume or a joint spacing are never inflated.
- Roof area uses the slope factor √(rise² + 144) ÷ 12 applied to the plan area. A regular hip roof has the same surface area as a gable roof over the same footprint and pitch, so the hip roof calculator prints both ways of working it out.
- Wall area deducts 21 sq ft per door and 15 sq ft per window by default. That is a standard trade allowance for a 3 × 7 ft door and a 3 × 5 ft window, not a code figure, and you can change the counts.
- Control joint spacing on the concrete slab calculator uses the trade rule of 2.5 × slab thickness in inches, capped at 15 ft. The IRC sets no joint spacing for slabs on grade, and the tool says so.
- Stair tools flag an intermediate landing at 12 ft 0 in of total rise, the AWC DCA 6 limit. IRC R311.7.3 alone allows 12 ft 7 in per flight; the stricter figure is used and both are stated.
Values the calculators ask you to enter instead of looking up
Where a number depends on a table this site cannot reproduce or has not verified, the calculator asks you for it and tells you where to find it. Concrete footing width comes from your soil and your building department. Gravel and crushed stone density varies by quarry and moisture, so the gravel calculator takes the figure from your supplier. Grout coverage per bag is a manufacturer chart, so the grout calculator takes it from your bag. The baluster maximum opening defaults to the 4 in IRC sphere and stays editable, because some guard positions and some local codes use a different figure.
What these construction calculators do not do
- No cost or price estimates, no labour rates.
- No structural design. The tools reproduce prescriptive tables; members, loads and connections outside those tables need a licensed engineer.
- No wind or seismic design, no point loads such as hot tubs or roofs over decks.
- No local amendments. Your county may change the IRC, as Seattle does for deck loads. Its version is the one that gets inspected.
- No habitable attics in the ceiling joist tool. Those are floors, so it sends you to the floor joist calculator.
The full terms are in the disclaimer.
Reporting a value that does not match the code book
If a number here disagrees with your copy of the code, send it through the contact page with the calculator, the inputs you used and the table and page you checked. The cell is compared with the source PDF. If the site is wrong it is fixed; if the published code is wrong, the cell is documented the same way as the misprints above. Background on reading these tables is in how to read a span table and live load vs dead load, and the stair limits are explained in the IRC stair code guide.
Questions about the calculator sources and rounding
Can you interpolate between values in an IRC span table?
Only where the table says so, and these calculators never do. IRC header Table R602.7(1) permits interpolation between building widths in footnote c, but many span tables carry no such note, and building code forums disagree on how far that permission reaches. Rather than take a side, every calculator here snaps up to the next printed value, which is always the conservative direction. You lose a little span, and in exchange every result matches one cell you can find on the printed page and show to an inspector.
What happens if my snow load or span is past the end of the table?
The calculator reports that the result is outside the table and gives no number. Extending a table past its last column is extrapolation, and the IRC does not permit it: a 70 psf column says nothing reliable about 80 psf. IRC R301.2.3 also sends buildings in areas with more than 70 psf ground snow to engineered design. Your options are a closer spacing, a higher grade, a deeper member, an extra beam or post to shorten the span, or an engineer. The tool suggests the ones that apply to your inputs.
Why do online span charts give different numbers for the same joist?
Mostly because they are copied from different tables, or copied wrong. Floor, ceiling, rafter and deck joist tables use different loads and deflection limits, so the same 2x8 has several correct answers. Some charts put floor joist values on deck pages, apply a species percentage the code never prints, or drop a footnote. Others quietly use a local amendment. Each result here names the exact IRC table and the Seattle PDF page it was read from, so when two numbers disagree you can open that page and see which one matches the printed code.
Which edition of the IRC do the calculators use?
The 2021 International Residential Code, for every span, stair and guard limit, plus AWC DCA 6-2015 for deck footing sizes. Many US jurisdictions still enforce the 2018 or 2015 IRC, and most adopt the code with local changes. Check which edition your building department has adopted, and whether it amended the table, before you rely on any number. The citation under each result gives the table number and source page, which makes it quick to compare against the edition and any local changes your inspector is using.
Are deck joist spans the same as floor joist spans?
No. Deck joists come from IRC Table R507.6, which assumes No.2 lumber with wet service and incising factors applied, 40 psf live load or 50 to 70 psf ground snow, and 10 psf dead load. Floor joists come from Tables R502.3.1(1) and (2), which assume dry interior lumber at 30 or 40 psf live load. The deck table gives shorter spans for the same size because those wet service factors reduce the allowed stresses. Using an indoor floor joist span for a deck overstates what the joist can carry, which is one of the commonest errors in online deck charts.
Why do Douglas fir, hem-fir and spruce-pine-fir show the same deck spans?
Because IRC Table R507.6 prints them as one row. Its footnote groups Douglas fir-larch, hem-fir and spruce-pine-fir together, with incising factors already included, so the three species share every deck joist span, while southern pine gets its own row with longer spans. A 2x8 at 16 in on center spans 11 ft 1 in for the grouped species and 11 ft 10 in for southern pine at 40 psf. Charts that list a different number for each of the three species have not been read from the IRC deck table.
Should I use the AWC span calculator or the IRC tables?
Use the IRC tables for a permit, and the AWC calculator when your lumber is not in them. The American Wood Council publishes both the tables the IRC reproduces and an online span calculator covering every species and grade in the NDS supplement. The IRC tables cover four species groups at fixed loads, which is what most inspectors check against. If you are using an uncommon species or grade, the AWC calculator is the better source, but confirm your building department accepts it. The calculators on this site reproduce the IRC tables only.
Why does the tool ask for footing width or gravel density instead of giving it?
Because a reliable table for those numbers is not one this site can reproduce and check. Footing width depends on soil bearing capacity and local rules, gravel density changes with the quarry, stone size and moisture, and grout coverage per bag is set by each manufacturer. A default that looks exact but is wrong for your material would be worse than a blank. So the calculator asks you for the figure, says where to get it, and then does the arithmetic. Your supplier, bag label or building department has the number that applies to your job.
Why does a result say a value is misprinted in the published IRC table?
Because the published 2021 IRC table has a wrong number in that cell. Where it can be recovered from a sister table the tool shows the corrected value and the printed one; the full list is in the rafter table misprints post.
I found a value that does not match my code book. What should I do?
Send it through the contact page with the calculator name, your inputs, and the table and page you compared against. The value is checked against the source PDF. If the site entered it wrong, it is corrected. If your code book differs because your jurisdiction amended the table or uses another edition, you will be told which, since your local version is the one that applies. If the published IRC itself is wrong, the cell is documented like the rafter misprints on this page. Reports like this are how copy errors in span tables get caught.