Corner bead calculator
8 outside corners at 8 ft plus 4 window returns at 5 ft come to 84 linear feet of corner bead, or 92.4 with 10% waste, which means 12 sticks of 8 ft. Count corners and returns once and skip the second trip mid-mudding. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Outside corners
- 8
- Wall height
- 8
- Opening returns
- 4
- Return height
- 5
- Waste
- 0.1
- Waste percent
- 10
- Waste length
- 8.4
- Outside lf
- 64
This corner bead calculator estimates how many linear feet of metal or paper corner bead you need once you know how many outside wall corners receive vertical bead and how many opening returns (window and door jamb edges) also take bead. It multiplies outside corners by wall height, multiplies opening returns by return height, adds those runs into a net length, optionally applies a waste fraction for cuts and damaged sticks, and ceils the order into whole stock sticks of a chosen length. Metal L-bead and paper-faced bead share the same geometric take-off: under-ordering means a second trip mid-mudding, while over-ordering unused eight-foot sticks wastes budget. A common check uses eight outside corners at eight feet, four returns at five feet each, and ten percent waste, which yields a stable linear-feet figure and stick count instead of a rough aisle guess. The engine is pure deterministic arithmetic with no network calls, no sampling, and no date-dependent shortcuts.
What you can do with it
DIY drywall finish shopping lists
Homeowners count outside corners and window returns on a sketch, set ceiling height and return heights, and know how many linear feet and 8-ft sticks of metal or paper bead to buy.
FAQ
What is the difference from a drywall sheet calculator?
A sheet calculator sizes boards from wall and ceiling area. This tool only estimates metal or paper corner bead linear feet from outside corners and opening returns you already counted.
When should I change the default waste or stick length?
Leave waste at 0.1 (10%) for typical residential cuts; set 0 for a pure geometric take-off.
Is the corner bead calculator free?
The browser tool runs free on your device.
Do inside corners need corner bead?
Usually not. Inside corners where two drywall faces meet are normally finished with paper tape rather than outside corner bead, so leave them off this count and only mark the outside L-corners.
What counts as an opening return?
Any edge around an opening that also gets bead: the vertical returns at window reveals, door jamb returns finished with bead, and arched openings where paper or vinyl bead is bent around the curve.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/home/corner-bead \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"outside_corners":8,"wall_height":8,"opening_returns":4,"return_height":5}'const res = await fetch("https://api.kit.forhosting.com/home/corner-bead", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"outside_corners": 8,
"wall_height": 8,
"opening_returns": 4,
"return_height": 5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/home/corner-bead",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"outside_corners": 8,
"wall_height": 8,
"opening_returns": 4,
"return_height": 5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/home/corner-bead", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"outside_corners":8,"wall_height":8,"opening_returns":4,"return_height":5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"outside_corners":8,"wall_height":8,"opening_returns":4,"return_height":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/home/corner-bead", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"outside_corners": 8,
"wall_height": 8,
"opening_returns": 4,
"return_height": 5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "home.corner_bead",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Use it free in the browser for DIY shopping lists and contractor take-offs, or call the API at $0.002 per successful request when estimating software needs the same contract.
Count outside corners and opening returns on the elevation plan
Walk every wall elevation and mark every outside corner where two drywall faces meet at an external L that will receive metal or paper corner bead from floor plate to ceiling line. Separately count every opening return edge that also takes bead—typical cases are the vertical returns at window reveals, door jamb returns finished with bead, and arched openings where a paper or vinyl bead is bent around the curve. Interior inside corners usually take paper tape rather than metal outside corner bead, so leave those off this take-off. Consistent counting across plan revisions is what keeps purchase orders honest when the architect adds a window or removes a jog that used to need bead. Send that count as outside_corners; accepted aliases include corners, outside_corner_count, corner_count, and l_corners so spreadsheet headers and form fields can reuse familiar labels. Send that count as opening_returns; aliases returns, return_count, opening_return_count, and window_returns cover common takeoff column names. Both counts are required non-negative integers: zero is valid when a straight remodel has no outside corners or no returned openings in this line item, but negative values, non-integers, empty strings, and missing fields fail with invalid_input and are not billed. Extremely large counts above the published maximum are rejected so multiplies stay stable on a Worker isolate. Do not invent corners from room perimeter alone—this endpoint does not measure plate length or on-center framing; it only multiplies the bead runs you already marked.
How wall height, return height, waste, and stick count are computed
Each outside corner is treated as a full-height bead run: outside_lf equals outside_corners multiplied by wall_height. wall_height must be a strictly positive finite number in any consistent linear unit (feet are conventional in U.S. residential work; metres work if every length uses metres). Aliases height, ceiling_height, corner_height, and H map to the same field. Each opening return uses return_height of bead: returns_lf equals opening_returns times return_height. return_height must be non-negative; when opening_returns is greater than zero it must be strictly positive so a zero-length return cannot silently hide a positive count. Aliases return_length, opening_height, return_run, and R cover schedule labels. Net linear feet is outside_lf plus returns_lf. Optional waste is a non-negative fraction of that net run, defaulting to one tenth (ten percent) for cuts, scarf joints, and damaged sticks; aliases waste_fraction, waste_factor, scrap, allowance, and overage are accepted, with a maximum of two (two hundred percent). linear_feet equals net_lf times one plus waste. Optional stick_length defaults to eight (common eight-foot metal bead sticks); aliases stock_length, piece_length, bead_length, and stick rename it. sticks is the ceiling of linear_feet divided by stick_length so you order whole sticks at the merchant. Optional precision chooses decimal places for non-integer numeric fields, defaulting to four and capped at fifteen so JSON goldens stay stable. The response echoes inputs with defaults filled, reports outside_lf, returns_lf, net_lf, waste_length, linear_feet, sticks, unit, method corners_and_returns, a formula string, a human-readable message, and step strings. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, random seed, or wall clock.
API usage, pricing, drywall workflows, and practical limits
Call the free in-browser corner bead calculator for quick site estimates, lumber-yard kiosks, and contractor whiteboards without standing up a spreadsheet. POST a JSON body with outside_corners, wall_height, opening_returns, and return_height, plus optional waste, stick_length, and precision when defaults do not match your shop standard. Use the prepaid API when a renovation app, quantity-takeoff pipeline, modular home configurator, or estimating tool needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with a drywall sheet calculator for board counts and with a corner stud calculator for framing packs so the full finish package covers boards, screws, bead, and mud. Remember that paper-faced bead, metal L-bead, bullnose, and vinyl arch bead share the same linear take-off even when the product SKU differs—select the product after you know linear_feet and sticks. Authors shipping SDKs can map linear_feet into purchase orders while showing outside_lf and returns_lf as explanatory detail for the estimator and inspector. This capability does not size joint compound bags, mesh tape, or inside-corner paper tape, and it does not auto-detect corners from a CAD drawing; you enter counts and heights that match the elevations you already measured.
Integration use cases
Lumber yard and ecommerce takeoff tools
Retail sites compute corner-bead linear feet and stick counts as shoppers toggle waste and stock stick length, using one deterministic API for quotes and carts.
Contractor bid automation
Estimating tools batch corner and return counts from plan markup, apply shop waste standards, and emit linear_feet and sticks for purchase orders without spreadsheets.
Technical questions
How does the corner bead calculator work?
It multiplies outside_corners by wall_height and opening_returns by return_height, sums those runs, multiplies by (1 + waste) for linear_feet, and ceils by stick_length for whole sticks. Method is always corners_and_returns.
What if outside_corners is negative or return_height is missing?
The request fails with invalid_input. Counts must be non-negative integers; wall_height must be positive; return_height must be non-negative (and positive when returns exist). Missing required fields are rejected and not charged.