Angle Converter

How to Convert an Angle

Features

Same Point on Earth, Two Numbers

Look up the Eiffel Tower on an old survey document and you'll find it at 48°51′29.6″N, 2°17′40.2″E. Look it up on a modern mapping API and it comes back as 48.858222, 2.294500 — the exact same location, described by two completely different number formats that don't look related at a glance. Degrees-minutes-seconds is the older, sexagesimal convention borrowed from Babylonian astronomy roughly 4,000 years ago; decimal degrees is what GPS receivers, mapping software, and spreadsheets actually store internally, because a single decimal number is far easier to compute with than three separate numbers glued together. Anyone moving between an old land survey, a printed map, and a modern GPS app ends up needing to translate between the two on a fairly regular basis. Degrees aren't even the only system competing for that space, either — the same French Revolutionary push that gave the world the metric system also tried to decimalise angles, dividing a right angle into 100 gradians instead of 90 degrees so that a full circle became a clean 400. It never displaced degrees the way the metre displaced older length units, but it survives today in European surveying and civil engineering software specifically because 100 grad is a tidier number to compute slopes against than 90 degrees — a 45° incline is a clean 50 grad, while a 30° incline becomes an untidy 33.333… grad, a trade-off Revolutionary-era engineers were happy to make in exchange for decimal consistency everywhere else.

Why Mathematicians Insist on Radians

Degrees are arbitrary — 360 is a Babylonian choice, convenient because it has so many divisors, but nothing about the number is mathematically necessary. A radian is different: it's defined as the angle where the arc length along a circle exactly equals the radius, which makes it dimensionless in a way degrees never are. That property has a real consequence in calculus — the derivative of sin(x) is exactly cos(x) only when x is measured in radians; work in degrees and a stray π/180 factor contaminates every derivative you take. Every major programming language's trigonometric functions expect radians for precisely this reason, which is also why feeding a raw degree value intoMath.sin() is one of the most common silent bugs in code that touches geometry — the function doesn't throw an error, it just quietly returns a mathematically wrong answer that looks plausible enough to pass an unwatched code review.

A Surveyor, a Sniper, and a Sailor

A land surveyor pulls up an old deed listing a boundary bearing in degrees-minutes-seconds and needs it in decimal to plug into modern GIS software — the DMS calculator below turns that conversion into a five-second lookup instead of hand arithmetic. A precision shooter dialling in a scope has to know whether their turret clicks in true minutes of angle or the rounded "shooter's MOA" many manufacturers use instead — a roughly 4.5% difference that matters enormously at long range and barely at all up close. A sailor reading a compass heading of 205° converts it mentally to "roughly southwest" without needing exact degrees, which is exactly what the compass bearing hint under this tool's main result is built to shortcut, faster than mentally stepping through all sixteen points of a compass rose. And a soldier cross-referencing a foreign optic marked in 6,000ths has to remember that's an artillery mil, not the 6,400ths NATO mil their own equipment uses — mixing the two up introduces a real aiming error, not just a rounding difference. An electrical engineer, in a quieter corner of the same problem space, describes a signal's phase shift as a fraction of a full turn rather than in degrees or radians, because a turn maps directly onto one complete cycle of a waveform — 0.25 turns is a quarter-cycle regardless of the signal's actual frequency, which makes it a genuinely convenient unit for anyone working with oscillations rather than static geometry. And an amateur astronomer checking a star chart runs into arcminutes and arcseconds constantly — the full Moon spans about 30 arcminutes of sky as seen from Earth, and modern star catalogues pin down stellar positions to a fraction of an arcsecond, a level of precision that only means anything once you know exactly how small a slice of a degree that actually is.

Built to Answer the Next Question, Not Just the First

Most angle converters stop at a single converted number. This one adds three things that answer the question that usually comes right after. Every result includes a compass bearing hint — normalising whatever you've entered to the nearest of 16 points around the compass rose — and, when the target unit is radians, a π-fraction hint for the common trigonometry angles (π/4, 2π/3, and so on) that most trig problems and exam answers are actually built around. The DMS ⇄ Decimal calculator below the main converter handles GPS-style coordinates in either direction, accepting degrees, minutes, and seconds and returning a clean decimal figure, or the reverse. And three filter chips above the full unit table — Mathematical, High Precision, Military & Optics — keep a quick degrees-to-radians check from sharing space with mils and arcseconds it has no use for. Precision works the same way it does across the rest of this converter family: Auto keeps everyday numbers short and readable, while a fixed 2, 4, 6, or 8 decimal-place setting exists for the moment an astronomy calculation or a survey record needs one consistent format all the way down to the arcsecond, rather than whatever looks tidiest on screen.

Where This Protractor Stops

This tool converts angle values between units — it does not perform geometry itself, so it won't calculate a missing triangle angle, a bearing between two coordinates, or a rotation matrix. The compass bearing hint is a quick intuition check, not a substitute for a properly corrected magnetic bearing, which also needs to account for local magnetic declination that varies by location and drifts slowly over time. And while every conversion factor here is mathematically exact, DMS coordinates pulled from an old document or a historical survey may themselves have been rounded or recorded to a coarser precision than this tool can restore — the calculator is only as accurate as the number you feed it. Nothing typed here is sent anywhere: the arithmetic runs as plain JavaScript inside the browser tab, with no server call and nothing logged, which matters for confidential survey coordinates or proprietary optical specifications as much as for a homework problem, and the tool keeps working identically with no internet connection at all once the page has loaded. For anything with legal or safety weight behind it — property boundaries, weapon zeroing, navigation charts — treat the output as a fast, accurate conversion and confirm it against the original authoritative source or calibrated instrument.