Everyday use · 2026-02-17 · Sophie Carter

Degrees and Radians Without Guesswork

CAD exports, trig homework, and CNC programs mix degrees and radians—convert angles with a workflow that catches quadrant and rounding mistakes.

A student enters 45 into a calculator expecting radians; the homework grading script assumes degrees. A machinist reads 1.5708 on a CAM output and wonders if that is 90 degrees or 100 millimeters of feed. Angles are simple until two teams use different unit conventions on the same part.

This guide follows those mixed-unit scenarios and shows how to convert confidently with an Angle Converter.

The scenario: same rotation, two notations

Degrees divide a circle into 360 parts—familiar from compass headings and CAD rotation tools. Radians measure arc length relative to radius: a full turn is 2π radians, a quarter turn is π/2 radians. Software libraries (JavaScript Math.sin, Python math, many game engines) expect radians unless documented otherwise.

Scenario-first: note which convention each tool uses before you paste a number.

Anchor conversions to remember

  • 180° = π radians ≈ 3.14159 rad.
  • 90° = π/2 rad ≈ 1.5708 rad.
  • 45° = π/4 rad ≈ 0.7854 rad.
  • 360° = 2π rad ≈ 6.28319 rad.

If a value near 1.57 shows up in code, think radians for a right angle. If a value near 90 shows up on a drawing, think degrees.

Quadrants and sign

Negative angles rotate clockwise in many conventions. Normalizing angles to 0–360° or 0–2π before conversion avoids comparing values in different quadrants. Add 360° (or 2π) to negative results when the application expects positive headings.

Worked example: trig calculation pipeline

Compute sin(45°). In radians, 45° is π/4 ≈ 0.785398. Libraries return sin(0.785398) ≈ 0.7071. If you forget conversion and take sin(45) in radians mode, you are evaluating a huge angle unrelated to the geometry—red flag when results exceed ±1 for basic trig.

Run the converter on the input angle, feed the radian output to the function, and document the step in lab notebooks.

CAD, GIS, and CNC notes

Some CAD dialogs allow decimal degrees, DMS (degrees-minutes-seconds), or radians. GIS bearings may use grads or mils in specialized fields. CNC posts may emit degrees while the controller expects radians for arc interpolation—check the post-processor sheet, not only the on-screen preview.

DMS conversions

45°30′15″ means 45 + 30/60 + 15/3600 degrees in decimal form before radian conversion. Convert DMS to decimal degrees first, then to radians. Mixing minutes into radian fields directly is a classic homework error.

Practical workflow

  1. Identify the source convention on the label or API docs.
  2. Normalize sign and range.
  3. Convert with the calculator; keep extra digits for intermediate steps.
  4. Round only for display on drawings or UI.
  5. Verify with a known angle (30°, 45°, 90°).

Sanity checks

Double an angle in degrees, convert to radians—should equal converting once and doubling in radians within tolerance. Inverse checks: convert radians back to degrees and compare to the drawing.

Navigation bearings and wraparound

Compass bearings use 0–360° clockwise from north. Converting a bearing of 350° to radians for library math, then adding 20° for a course correction, requires normalization: 350° + 20° = 10°, not 370° on the compass rose. Always reduce modulo 360° before radian conversion when the API expects principal values.

Grads and mils (specialized fields)

Some surveying and military tools use grads (400 per circle) or mils. If a legacy PDF lists 100 grads, convert to degrees (90°) before radians. Unfamiliar units on old drawings are a common source of “almost right” parts.

Teaching and grading workflows

Instructors can require students to show degree input, radian intermediate, and rounded final answer. That paper trail catches mode errors faster than red ink on the final number alone.

Rotation matrices and game engines

Graphics pipelines apply radians in matrix functions. A 90° UI rotation exported as 90 in a JSON config without a unit flag will spin the wrong amount. Add "unit": "deg" or convert at export time and document which you chose.

Inverse trig and domain errors

asin and acos outputs are radians. Convert results to degrees for human-readable diagrams. Domain errors often mean the input was already in the wrong unit—fix the convention before chasing “broken libraries.”

Robot joint limits

Joint soft limits in radians may be entered by integrators while teach pendants show degrees. Convert limits when copying from OEM PDFs to your safety PLC. A few milliradians error at the flange can mean centimeters at the tool tip.

Spreadsheet trig functions

Excel and Google Sheets use radians in SIN, COS, and TAN unless you wrap with DEGREES. Build a template column “angle_deg” and “angle_rad” side by side so reviewers see both.

Wind turbine yaw offsets may be documented in degrees while SCADA historians store radians—convert when merging OEM manuals with live tags.

Wind turbine yaw offsets may be documented in degrees while SCADA historians store radians—convert when merging OEM manuals with live tags. Laser layout tools often export decimal degrees; confirm before feeding control software.

Try it before the next CAM or homework session

Keep a sticky note: “library radians, drawing degrees.” Use the Angle Converter at the boundary. Fewer scrapped parts, fewer late-night trig surprises.