Angle of a right triangle from two sides, in degrees

In a right triangle, each acute angle is locked in by the ratio of two sides: opposite over hypotenuse gives the sine, adjacent over hypotenuse gives the cosine, and opposite over adjacent gives the tangent. Reversing those ratios with inverse trigonometric functions recovers the angle itself. That is the everyday calculation behind roof pitches, ramp inclinations, ladder safety angles, and homework problems that hand you two lengths and ask how steep the corner is. This capacity accepts exactly two side lengths named by their role relative to the angle you want — opposite, adjacent, or hypotenuse — so you never have to decide which leg is which.

How two sides of a right triangle determine an acute angle

A right triangle has one ninety-degree angle, so its two acute angles always sum to ninety degrees. Once you know any two side lengths, the shape of the triangle is fixed and each acute angle follows from a single ratio. If the two known sides are the leg opposite your angle and the leg adjacent to it, their quotient is the tangent of the angle, and the two-argument arctangent turns that ratio back into degrees.

If you know the opposite leg and the hypotenuse, the quotient is the sine and the inverse sine gives the angle. If you know the adjacent leg and the hypotenuse, the quotient is the cosine and the inverse cosine does the job. Search intent clusters around phrases like angle of a right triangle from two sides, find angle given opposite and adjacent, inverse tangent calculator, and roof pitch angle from rise and run.

People want a numeric answer they can check against a worksheet key, a building code table, or a CAD note — not a lecture on trigonometry. Naming the inputs by their geometric role (opposite, adjacent, hypotenuse) instead of generic leg labels removes the most common mistake in this calculation: swapping which side is which and silently getting the complementary angle. The response spells out which inverse function was used, so the result stays auditable when you paste it into notes, a report, or an automated test.

Input validation, the three formulas, and how the result is computed

The engine counts the provided fields: fewer than two leaves the angle under-determined, all three over-specifies the problem and can hide inconsistent data, so only pairs proceed. When both legs are given, the angle is the two-argument arctangent of opposite over adjacent, converted from radians to degrees. When the opposite leg and hypotenuse are given, the engine first verifies the hypotenuse is strictly longer than the leg — otherwise no real right triangle exists — and then applies the inverse sine of their ratio.

The adjacent-plus-hypotenuse case applies the inverse cosine after the same longest-side check. Edge cases are explicit and rejected early: a hypotenuse equal to a leg would force a degenerate zero-degree angle, a shorter hypotenuse is geometrically impossible, and missing or extra sides are counted and reported in the error message. The response includes the angle in degrees, the angle unit, the formula applied, and the method tag, so downstream code can assert on the whole contract rather than scraping a bare number.

Practical use, limits, pricing, and delivery channels

Use the browser tool when you need one quick angle — checking a ramp against an accessibility guideline, converting a roof's rise and run into a pitch angle, verifying a ladder leans within the recommended seventy-five-degree zone, or confirming a trigonometry exercise without installing a computer-algebra system. Side lengths can be in any unit you like — millimetres, inches, metres — because the angle depends only on the ratio, and the response carries that unit independence by reporting degrees alone.

Accepted inputs must describe a genuine right triangle: exactly two positive sides, with the hypotenuse strictly the longest side when present. Results are fully deterministic: the same two lengths always yield the same angle and the same formula field. There is no language model, no external geometry service, and no randomness in the computation path, so the capacity is safe to pin in reproducible lesson materials, contest answer checkers, and regression suites.