ForHosting KIT · Developer Utilities

Thirty-sixty-ninety triangle solver

A thirty-sixty-ninety triangle has one right angle and two acute angles measuring thirty and sixty degrees.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Those fixed angles force its short leg, long leg, and hypotenuse into the permanent ratio one to the square root of three to two. This solver accepts any one positive side, identifies its role, and calculates the complete set of side lengths with deterministic arithmetic. It is useful for checking geometry work, preparing dimensions, and building repeatable calculations without entering angles or choosing a general trigonometric formula. The browser version runs locally, while an API request costs $0.002.

Understand the special side ratio

Every thirty-sixty-ninety triangle is similar to every other triangle with the same three angles. Similarity is why one fixed ratio solves the entire family: short leg to long leg to hypotenuse equals one to the square root of three to two. The short leg is always opposite the thirty-degree angle, the long leg is opposite the sixty-degree angle, and the hypotenuse is opposite the ninety-degree angle. If the short leg is represented by x, the long leg is x multiplied by the square root of three and the hypotenuse is two x. This relationship can also be derived by cutting an equilateral triangle in half through its altitude. The cut creates two congruent right triangles, halves the original base, and leaves the altitude equal to root three times the half-base. Because the ratio depends on side roles, a bare number is not enough input. A length of ten could be the short leg, the long leg, or the hypotenuse, producing three differently scaled triangles. Always identify which side the measurement represents before applying a formula or using the solver.

Enter one side and interpret the result

Provide side as a positive finite number and set side_type to short, long, or hypotenuse. Choose short when the known side lies opposite the thirty-degree angle. Choose long when it lies opposite the sixty-degree angle. Choose hypotenuse for the side opposite the right angle, which is also the triangle's longest edge. The response returns all three named sides so the known value appears alongside the two calculated values. It also echoes the selected role in given and includes the ratio as a readable reminder of the method. When the short leg is known, the solver multiplies it by root three and by two. When the long leg is known, it first divides by root three to recover the short leg. When the hypotenuse is known, it first divides by two. Outputs are rounded to fifteen significant digits, which keeps ordinary decimal results stable while preserving useful precision across small and large accepted measurements. The solver does not attach physical units, so all returned sides use whatever consistent unit the input represents, whether centimeters, meters, inches, or an abstract coordinate scale.

Validate calculations and avoid common mistakes

A quick validation starts with ordering: for every positive input, the short leg must be smaller than the long leg, and the long leg must be smaller than the hypotenuse. Next, divide the long leg by the short leg; the result should be approximately 1.732, the square root of three. Dividing the hypotenuse by the short leg should give exactly two within displayed precision. You can also check the Pythagorean theorem: short squared plus long squared equals hypotenuse squared, because x squared plus three x squared equals four x squared. The most frequent mistake is assigning a side to the wrong role. A diagram may be rotated or reflected, so do not guess from whether an edge looks horizontal, vertical, left, or right; use the angle opposite it. Another mistake is multiplying when division is required. Given the long leg, divide by root three before doubling the recovered short leg. Given the hypotenuse, halve it first. Zero, negative, missing, nonnumeric, infinite, and out-of-range side values are rejected as invalid input rather than producing a degenerate or misleading triangle. Successful API requests use the base price $0.002.

Geometry homework checks

Verify missing-side calculations for special right-triangle exercises from any one supplied side.

Drafting dimensions

Recover consistent leg and diagonal lengths for a known thirty-sixty-ninety layout.

Procedural geometry

Generate repeatable special-triangle dimensions for code, graphics, simulations, or test fixtures.

What is the thirty-sixty-ninety side ratio?

The short leg, long leg, and hypotenuse have the ratio 1:root-three:2.

Which side is the short leg?

The short leg is opposite the thirty-degree angle.

How do I solve from the long leg?

Divide the long leg by the square root of three to get the short leg, then double the short leg for the hypotenuse.

How do I solve from the hypotenuse?

Divide the hypotenuse by two for the short leg, then multiply that result by the square root of three for the long leg.

Does the solver use degrees or radians?

Neither needs to be entered because the angles are fixed at thirty, sixty, and ninety degrees.

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.

POSThttps://api.kit.forhosting.com/trig/thirty-sixty-ninety

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.

curl -X POST https://api.kit.forhosting.com/trig/thirty-sixty-ninety \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"side":6,"side_type":"short"}'
{
  "side": 6,
  "side_type": "short"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "trig.thirty_sixty_ninety",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →