Feet and inches
Split a length in inches into whole feet plus leftover inches, so 74 inches becomes 6 ft 2 in, written 6′ 2″ on drawings. Handy for height forms, lumber tickets and sewing patterns. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Inches
- 74
- Result
- 6 ft 2 in
- Feet
- 6
- Remaining inches
- 2
- Formatted
- 6 ft 2 in
A total length written only in inches is awkward on lumber tickets, tape-measure notes, height forms, sewing patterns, and shipping labels that expect a mixed imperial pair: whole feet plus leftover inches that do not fill another foot. This feet and inches converter takes a single finite nonnegative length in inches and splits it with the exact identity that one foot equals twelve inches. Seventy-four inches becomes six feet and two leftover inches; twelve inches becomes one foot with nothing left over; zero stays zero feet and zero inches.
How a total inch count becomes whole feet and leftover inches
People often record a length as one number of inches because a tape, a ruler, a product spec, or a spreadsheet cell holds a single figure. Imperial speech and most United States forms do not stop there: they want a mixed pair of whole feet plus leftover inches that stay strictly below twelve. The conversion is therefore an integer split against an exact constant, not an approximate lookup table and not a decimal-foot result such as 6.17 ft.
One foot is twelve inches by definition, so divide the given total by twelve, take the integer number of complete groups as feet, and keep the remainder as leftover inches. Seventy-four inches is six complete feet and two leftover inches because six times twelve is seventy-two and two remain. Thirty-six inches is exactly three feet with zero leftover inches.
Fourteen and a half inches is one foot and two and a half leftover inches. Zero inches converts to zero feet and zero leftover inches, which is the honest empty-length case for a cleared field. This capability never converts centimetres, never uses survey-foot variants, never rounds to the nearest half-inch as a hidden default, and never invents a second input unit.
The same identity appears in the formula field so a student or a user interface can reprint the working next to the answer without reconstructing the arithmetic from scratch.
Where a feet-and-inches split earns its keep, and what it costs
Lumber yards, framing crews, and cabinet shops often measure a board, a stud, or a cut list as a single inch count from a tape and must print the mixed pair that invoices, cut lists, and building notes still use. Height forms, sports rosters, and clothing size charts sometimes store stature as total inches from a stadiometer and need six-foot-two instead of seventy-four. Sewing patterns, curtain drops, and furniture listings convert a leftover-inch remainder so a shopper who thinks in feet can compare a specification at a glance.
Shipping desks convert linear inches of a parcel dimension into a spoken feet-and-inches label when a carrier form and a warehouse ticket disagree on notation. Keep this landing focused on the search intent feet and inches—total inches in, mixed imperial pair out—and use a dedicated centimetre-height converter or a generic length table when the pipeline starts from metric units or needs a unit that is not this split. Source inputs follow the same retention rules as other KIT parse items; nothing is stored after the task completes.
What you can do with it
Lumber tickets and framing cut lists
Split a tape reading recorded as total inches into the whole-feet plus leftover-inches pair that cut lists, invoices, and building notes still print.
Height forms stored as total inches
Turn a stadiometer or roster value stored as seventy-four inches into a readable six-foot-two style label for paper forms and sports cards.
Sewing, curtains, and furniture specs
Convert a leftover-inch remainder from a single inch count so shoppers who think in feet can compare a drop, a cut, or a clearance at a glance.
FAQ
What happens if the length is negative or not a number?
Length must be a finite nonnegative number; missing, empty, NaN, Infinity, negative values, and non-numeric strings are rejected and are not billed.
Why return leftover inches instead of only a decimal number of feet?
Search intent for feet and inches is the mixed imperial pair people write on forms (for example 6 ft 2 in), not 6.1667 feet. The original total is still echoed as inches for callers who need it.
Is twelve inches per foot exact?
Yes. One foot equals twelve inches by definition of the international foot. No survey-foot variant and no approximate 30 cm shortcut is used; this split never converts metric units.
How do I convert inches to feet and inches by hand?
Divide the total by 12. The number of whole groups is the feet, and whatever remains is the leftover inches, always less than 12. For example, 36 inches is exactly 3 feet with nothing left over.
Can I enter fractions of an inch?
Yes. 14.5 inches becomes 1 foot and 2.5 inches. The leftover keeps its decimals and is never rounded to the nearest half inch behind your back, so you can round it yourself at the end.
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/conv/feet-and-inches \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"inches":74}'const res = await fetch("https://api.kit.forhosting.com/conv/feet-and-inches", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"inches": 74
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/feet-and-inches",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"inches": 74
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/feet-and-inches", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"inches":74}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"inches":74}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/feet-and-inches", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"inches": 74
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.feet_and_inches",
"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.
Limits
max_inches | 1000000000000 |
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
Negative values and non-numeric input fail with invalid_input and are not billed. Successful API calls cost $0.002 per item.
How a total inch count becomes whole feet and leftover inches
Leftover inches are rounded to twelve decimal places only so JSON goldens stay stable across runtimes; if that rounding would land on twelve, the extra foot is carried so the remainder stays in the half-open interval from zero inclusive to twelve exclusive.
Input contract, response fields, and error behaviour
Zero is a valid length and returns zero feet and zero leftover inches. The formatted field writes the mixed unit as N ft M in, display writes the common prime notation used on drawings, and result repeats formatted for callers that look for a single primary string. Formula restates feet equals floor of inches divided by 12, with leftover inches as the modulo. A short message and a steps array walk through the input, the twelve-inch definition, and the split, which tutoring software can show verbatim. Do not send mixed strings such as six-foot-two in quotes: parse the total inch count first, then call this split. POST a JSON body with the required field inches, a finite nonnegative number or a plain numeric string. Aliases value, length, total_inches, and in are accepted so forms, spreadsheets, and SDKs can use the name that already exists in the source record. Negative values, NaN, Infinity, empty strings, and non-numeric text fail with invalid_input naming the field, and those failures are not billed. Magnitudes above one trillion inches are rejected so Worker isolates stay safe. On success the body echoes the parsed inches value, returns feet as a whole number, and returns remaining_inches as the leftover remainder in the half-open interval from zero inclusive to twelve exclusive. The constant inches_per_foot 12 travels with the payload so a client can cache the identity without hard-coding it. Pair the numbers with your own rounding for a tape-measure card if you need half-inch display; this endpoint keeps twelve-decimal leftovers so automation can round last, not first.
Where a feet-and-inches split earns its keep, and what it costs
Successful API calls bill as one item at $0.002; invalid_input is free, so you can validate a form field without burning balance.
Technical questions
How do I convert a total length in inches into feet and leftover inches?
Send a finite nonnegative number in the inches field (aliases value, length, total_inches, in). The API takes whole feet as floor of that total divided by 12 and returns remaining_inches as the leftover remainder.
What does the feet and inches converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.