Lateral area of a cone
Give the base radius and the slant height of a cone and get the area of its curved side only, without the base: a radius of 3 and a slant height of 5 give 47.1238898038. Right for funnels, party hats and tepee covers. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Radius
- 3
- Slant height
- 5
- Lateral surface area
- 47.1238898038
- Formula lateral surface
- A_lateral = π r l
This calculator turns a positive base radius and slant height into the exact lateral surface area of a right circular cone: the curved side only, pi times r times l, with no base disk included.
What lateral surface area means and which length is the slant height
A right circular cone is the solid formed by rotating a right triangle about one of its legs: the base is a circle of radius r, and the apex sits directly above the center of that circle. Every straight line from the apex to a point on the rim of the base has the same length, and that length is the slant height l. Do not confuse it with the perpendicular height h, which runs from the apex straight down to the center of the base.
The two are related by the Pythagorean theorem, l = √(r² + h²), so if your measurements give you the perpendicular height you must convert before using this calculator, because feeding h in place of l silently shrinks the result. The lateral surface is the curved side of the cone: if you cut it along a generator line and unroll it flat, you get a circular sector whose radius is l and whose arc length is the base circumference 2 π r.
That unrolling is exactly why the area formula is π r l — the sector area is one half of arc length times radius, which collapses to π r l. This tool reports only that curved component, not the base disk π r² and not the total π r (r + l).
If you are wrapping an open funnel, a party hat, a teepee canvas, or any cone with no bottom, the lateral figure alone is precisely the number you want, and computing it directly avoids subtracting a base you never needed.
Validation rules, error handling, and edge cases
Every input is validated before any arithmetic happens. The same error covers Infinity and NaN, non-numeric strings such as "abc", and values of the wrong type such as booleans or arrays. There are a few geometric edge cases worth understanding.
A very small radius with a very large slant height is a valid needle-like cone and computes normally; floating-point rounding at the requested precision is the only distortion. A slant height smaller than the radius is geometrically impossible for a right cone, since l = √(r² + h²) implies l ≥ r, but this calculator deliberately does not enforce that inequality: it treats radius and slant height as two independent positive lengths and applies π r l literally, which keeps the contract simple and predictable.
For cones where you know the perpendicular height instead, compute l = √(r² + h²) first, and for closed solids that also need the base disk, use a total cone surface area tool instead.
What you can do with it
Material estimates for open conical parts
Size fabric for teepees and party hats, sheet metal for funnels and hoppers, or paint coverage for the curved side of conical roofs from measured radius and slant height, with no base area inflating the estimate.
FAQ
What does the lateral area of cone calculator cost?
It is free in your browser on this page.
What if radius or slant height is zero or negative?
The same applies to Infinity, NaN, and non-numeric strings.
I know the perpendicular height, not the slant height. Can I use this?
Convert first with the Pythagorean relation l = √(r² + h²), then call with radius and the computed slant height. Feeding the perpendicular height directly would understate the lateral area.
Does the result include the circular base?
No. This tool returns only the lateral (curved) surface area π r l. If you also need the base disk π r² or the total π r (r + l), use a total cone surface area calculator instead.
Is the result deterministic and cacheable?
Yes. The computation is pure analytic geometry with no network, randomness, or clock access, so identical requests always return byte-identical responses at the requested precision.
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/math/lateral-area-of-cone \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"radius":3,"slant_height":5}'const res = await fetch("https://api.kit.forhosting.com/math/lateral-area-of-cone", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"radius": 3,
"slant_height": 5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/math/lateral-area-of-cone",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"radius": 3,
"slant_height": 5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/math/lateral-area-of-cone", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"radius":3,"slant_height":5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"radius":3,"slant_height":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/math/lateral-area-of-cone", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"radius": 3,
"slant_height": 5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "math.lateral_area_of_cone",
"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
You enter radius and slant height as finite positive lengths, as numbers or numeric strings; the engine returns the echoed radius and slant_height, the lateral_surface_area, and the formula string so a student, a reviewer, or a log line can verify the identity without reading the source. When radius or slant height is missing, zero, negative, or non-finite, the tool returns invalid_input instead of a silent NaN.
How to call the calculator and read the response
The optional precision field, an integer from 0 to 15 with a default of 10, controls how many decimal places the numeric fields carry in the response. Units are abstract and consistent: if you feed centimeters you get square centimeters, if you feed inches you get square inches, and if you feed meters you get square meters, with no hidden conversion anywhere in the pipeline. The request takes two required fields and one optional one. radius is the base radius of the cone and slant_height is the slant height; both must be positive finite numbers, and both accept numeric strings such as "2.5", which is handy when values arrive from form fields or CSV files. A valid call with radius 3 and slant_height 5 returns the echoed inputs, lateral_surface_area ≈ 47.1238898038, and the formula_lateral_surface string that states the identity A_lateral = π r l. The output is a flat JSON object, so you can assert on lateral_surface_area directly in a test or pipe it into a spreadsheet. Aliases r, R, and base_radius are accepted for radius, and l, slant, and l_slant for slant height, matching the params contract.
Validation rules, error handling, and edge cases
A missing, empty, zero, or negative radius or slant height is rejected with an invalid_input error whose message names the offending field and states that it must be a positive finite number. The precision field must be an integer between 0 and 15 inclusive; anything else, including fractional values or out-of-range integers, is also invalid_input. Failed requests are not charged, so you can probe the endpoint freely while integrating. If you need the consistency check, compare slant_height against radius in your own code and reject l < r before calling.
Integration use cases
Homework and exam preparation
Compute the curved surface area from textbook radius and slant height, verify hand work against the formula string, and confirm that non-positive dimensions are rejected with invalid_input.
Deterministic geometry fixtures
Generate reproducible lateral cone area values for unit tests, contest validators, and CI assertions without hand-rolled π r l arithmetic or floating-point surprises between machines.