Solving a Right Triangle From Any Two Given Values
A right triangle only ever needs the 90° corner plus two more independent facts to be fully determined, but those two facts can arrive in several different shapes. Rather than re-deriving a method every time a slightly different pair of clues shows up, it helps to recognise which of four patterns a problem matches, because each one has a fixed, short route straight to the answer. This walks through all four, back to back, using the same solver behind the right triangle calculator so every number here is the tool's real output, not a hand estimate.
The four patterns
Labelling the right angle's corner C, the acute angles A and B, and the sides a, b, c opposite them in the usual way (c is the hypotenuse), every solvable input reduces to one of these:
- Angle + hypotenuse. Sine and cosine each connect the angle to one leg directly.
- Angle + a leg. Depending on which leg, either tangent (the other leg) or sine/cosine (the hypotenuse) gets there first.
- Two legs. Pythagoras finds the hypotenuse; an inverse trig function finds an angle.
- A leg + the hypotenuse. Pythagoras finds the other leg; inverse sine or cosine finds an angle.
Two acute angles alone are never enough, no matter how precisely known, because angles alone fix a triangle's shape but not its size — you always need at least one length in the mix.
Pattern 1: angle + hypotenuse
Suppose A = 52° and the hypotenuse c = 15. Both legs come straight from sine and cosine:
a = c sin A = 15 × sin 52° ≈ 15 × 0.7880 ≈ 11.8202,
b = c cos A = 15 × cos 52° ≈ 15 × 0.6157 ≈ 9.2349.
The remaining angle is B = 90° − 52° = 38°. Running the same inputs through the calculator confirms a ≈ 11.8202, b ≈ 9.2349, B = 38°, area ≈ 54.5791, and perimeter ≈ 36.0551. Whenever the hypotenuse is one of your two knowns, sine and cosine reach both legs in a single step each — there is no need to solve for one leg and then fall back on Pythagoras for the other.
Pattern 2: angle + a leg
Now suppose A = 28° and the leg adjacent to it, b = 10. Since you know the adjacent leg and want the opposite one, tangent is the direct route:
a = b tan A = 10 × tan 28° ≈ 10 × 0.5317 ≈ 5.3171.
The hypotenuse follows from cosine: c = b / cos A = 10 / cos 28° ≈ 10 / 0.8829 ≈ 11.3257. The calculator's output matches: a ≈ 5.3171, c ≈ 11.3257, B = 62°, area ≈ 26.5855, perimeter ≈ 26.6428. Had the known leg instead been the one opposite A, the roles simply swap — tangent would still connect the two legs, just rearranged, and sine rather than cosine would reach the hypotenuse. Either way, the leg you already have and the leg you want determine the ratio; the angle never changes that logic, only the specific numbers.
Pattern 3: two legs, no angle
With both legs known and no acute angle given — say a = 7 and b = 24 — Pythagoras goes first:
c2 = 72 + 242 = 49 + 576 = 625, so c = √625 = 25.
That is the well-known 7-24-25 triple, a whole-number right triangle in the same family as 3-4-5 and 9-12-15. The angle opposite the shorter leg comes from an inverse tangent: A = tan−1(7/24) = tan−1(0.2917) ≈ 16.26°, and B = 90° − 16.26° = 73.74°. The calculator agrees exactly: c = 25, A = 16.26°, B = 73.74°, area = 84, perimeter = 56. Area here is simply ½ × 7 × 24 = 84, since the two legs are already perpendicular to each other.
Pattern 4: a leg + the hypotenuse
Finally, suppose a = 9 and the hypotenuse c = 41. The missing leg comes from Pythagoras rearranged:
b2 = c2 − a2 = 412 − 92 = 1681 − 81 = 1600, so b = √1600 = 40.
That is the 9-40-41 triple. The angle opposite the known leg comes from inverse sine, since a leg and the hypotenuse together mean SOH: A = sin−1(9/41) = sin−1(0.2195) ≈ 12.68°, and B = 90° − 12.68° ≈ 77.32°. The calculator confirms b = 40, A = 12.68°, B = 77.32°, area = 180, perimeter = 90. Notice the guard rail built into this pattern: a known leg can never be allowed to equal or exceed the hypotenuse, since the hypotenuse is always the longest side in a right triangle — feeding in a leg of 45 against a hypotenuse of 41 has no solution, and a correct solver should refuse it outright rather than silently returning a nonsense angle.
Cross-checking Pattern 2 with Pythagoras
Pattern 2's two trig steps are worth confirming against the one method that never uses an angle at all. From A = 28° and b = 10, tangent and cosine gave a ≈ 5.3171 and c ≈ 11.3257. Pythagoras should recover the same hypotenuse independently: c2 = a2 + b2 = 5.31712 + 102 ≈ 28.2716 + 100 = 128.2716, and √128.2716 ≈ 11.3257 — matching the calculator's own c ≈ 11.3257 exactly, confirming the tangent-and-cosine route and the Pythagorean route agree completely. Running a second, independent method against the first is a fast habit for catching a genuine mistake, since two unrelated calculations landing on the same answer (up to rounding) is strong evidence neither one went wrong.
A non-example: why two angles alone fail
It is worth seeing the failure case explicitly rather than just being told about it. Suppose you are given A = 40° and B = 50° and nothing else. Every check passes at first glance — the two angles are complementary, both are acute, and 40° + 50° + 90° = 180° as required. But try to find a single side length and the process stalls immediately: SOHCAHTOA needs a ratio of two sides, and you don't have even one. A triangle with a = 3, b = 3.5753, c = 4.6672 satisfies these same two angles, and so does one scaled up ten times to a = 30, b = 35.7526, c = 46.6717, and a million times that size again — every one of them is a valid answer, which really means none of them is the answer. A correct solver has to refuse this input outright rather than silently inventing a side length, which is exactly why the calculator requires at least one side no matter which combination of angle information you supply.
Checking your own work with area and perimeter
Once a triangle is solved, area and perimeter double as a sanity check on the whole calculation, since both should come out as ordinary, unremarkable positive numbers with no leftover surprises. For the 9-40-41 triangle above, perimeter = 9 + 40 + 41 = 90 and area = ½ × 9 × 40 = 180 — both clean, round numbers, which is a mild but real hint (not a proof) that a whole-number Pythagorean triple is in play. For the angle-driven examples, the numbers are messier but no less checkable: for Pattern 1 above, perimeter = 11.8202 + 9.2349 + 15 = 36.0551, matching the calculator's own perimeter figure exactly, and area = ½ × 11.8202 × 9.2349 ≈ 54.579, matching to the calculator's rounding. Recomputing perimeter and area independently from the solved sides is a fast way to catch a transcription error before it propagates into a larger problem.
Recognising the pattern quickly
In practice, the fastest way to classify a problem is to ask two questions in order: is the hypotenuse one of my two knowns, and is an acute angle one of my two knowns? A "yes" to the second question with the hypotenuse also known is Pattern 1; a "yes" to the second question with a leg known instead is Pattern 2; a "no" to the angle question with two sides known splits into Pattern 3 (two legs) or Pattern 4 (a leg and the hypotenuse), distinguished by whether the hypotenuse is one of the two given sides. Four short questions, four short methods — see How to Solve a Right Triangle for the underlying ratios these patterns all draw from, and SOHCAHTOA Explained for why the ratios work in the first place.
Whichever pattern your numbers match, the right triangle calculator solves it instantly and will tell you plainly if the two values you entered don't actually describe a triangle.
A note on units and modes
All four worked examples above used degrees, since that is the more familiar unit for a stand-alone triangle problem, but every ratio and inverse function used works identically in radians — the underlying sine, cosine, and tangent do not care which unit describes the angle, only that you stay consistent and tell your calculator which one you mean. If a problem hands you an angle in radians, either convert it to degrees first with the degrees to radians converter or make sure your calculator (and any tool you're using) is explicitly set to radian mode before entering it. Mixing the two modes mid-problem is one of the most common sources of a triangle that fails its own Pythagorean check by a wide margin, exactly the kind of error How to Solve a Right Triangle flags as the first thing to suspect when a result looks wrong.
None of the four patterns above require anything beyond the ratios and the Pythagorean theorem — the only real skill is correctly identifying which pattern you are looking at before you start writing equations, which gets faster with every triangle you work through by hand.