Skip to content
AI360Xpert
Beta

Angles, Radians and Degrees

Degrees split a turn into 360 slices while radians measure the arc the angle cuts, so one convention suits people and the other suits calculus and code.

A 60 degree angle is pi over 3 radians, and on a circle of radius 120 it cuts an arc of about 125.7, which is the radius times the radian angle
A 60 degree angle is pi over 3 radians, and on a circle of radius 120 it cuts an arc of about 125.7, which is the radius times the radian angle

Why Does This Exist?

Angles arrive in two languages and they collide constantly. People say 90 degrees, but every math library computes in radians, and calculus formulas like the derivative of sine only work in radians. Every ML practitioner meets the seam: a rotation written in degrees silently fed to a radian function, producing garbage with no error message.

The fix is to see the two units as one idea with two rulers. Degrees chop a full turn into 360 historical slices. Radians ask how many radii of arc the angle cuts out, which makes them the native unit of circles, calculus, and code. This page teaches both and the conversion, so the handoff between human-readable and machine-computable never breaks. The parent topic is trigonometry.

The one idea you need first

A full turn is the angle that brings you back to facing the way you started. Call that amount 1 turn. Degrees define it as 360, radians define it as 2π≈6.2832\pi \approx 6.283. Every conversion is just a fraction of a turn written in one ruler or the other.

Think of It Like This

A pizza cut two ways

Imagine a pizza and two ways to describe a slice. Degrees are the party convention: cut the whole pizza into 360 slices and count them, so a quarter pizza is 90. Radians are the cook's convention: lay the crust's radius along the edge and count how many fit, so a quarter pizza is about 1.57 radii of crust.

Same slice, two counts. The party count is easy to picture, which is why humans use it. The cook's count connects directly to how much crust there is, which is why formulas prefer it. Neither is wrong; trouble only starts when you order in slices and the kitchen hears radii.

How It Actually Works

One full turn equals both rulers at once:

360°=2π radians,180°=π radians360° = 2\pi \text{ radians}, \qquad 180° = \pi \text{ radians}

In plain words: degrees (°\degree) count 360ths of a turn, radians (rad) count radii of arc, and π\pi (pi, about 3.1416) is the number of half-turns in the conversion. To convert, multiply by the fraction that cancels the old unit:

radians=degrees×π180,degrees=radians×180π\text{radians} = \text{degrees} \times \frac{\pi}{180}, \qquad \text{degrees} = \text{radians} \times \frac{180}{\pi}

Radians earn their place with one formula degrees cannot match. An angle θ\theta in radians on a circle of radius rr cuts an arc of length s=rθs = r\theta. No conversion constant, just multiplication. That is why arc lengths, angular speed, and every calculus result involving angles are stated in radians.

Worked example

Convert 60°60° to radians and find the arc it cuts on a circle of radius 120:

60°×π180=π3≈3.14163≈1.0472 rad60° \times \frac{\pi}{180} = \frac{\pi}{3} \approx \frac{3.1416}{3} \approx 1.0472 \text{ rad}

Arc length: s=120×1.0472≈125.66s = 120 \times 1.0472 \approx 125.66. Check against the full circle: circumference is 2π×120≈753.982\pi \times 120 \approx 753.98, and one sixth of that (60 degrees is a sixth of a turn) is 753.98/6≈125.66753.98 / 6 \approx 125.66. Both routes agree, which confirms the conversion and the arc formula together.

Code

Convert once at the boundary and verify the arc two ways.

import numpy as np
theta = np.deg2rad(60)  # degrees in, radians outprint(round(theta, 4))              # -> 1.0472print(round(120 * theta, 2))        # -> 125.66print(round(2 * np.pi * 120 / 6, 2))  # -> 125.66

The arc from rθr\theta matches one sixth of the circumference, so the conversion is confirmed, not assumed.

Watch Out For

Mixing units inside one calculation

The classic wreckage: convert the input to radians but leave a threshold in degrees, or rotate by degrees then compare against a radian tolerance. Everything type-checks and every value is wrong.

Keep one unit per function and convert at the door. Name variables theta_rad or deg so the unit is visible, and treat any bare number near 3.14 or 57.3 (the degrees in one radian) as a unit-smell worth checking.

Assuming small-angle shortcuts work in degrees

The handy approximation sin⁡θ≈θ\sin \theta \approx \theta for tiny angles is true only in radians. In degrees, sin⁡1°≈0.01745\sin 1° \approx 0.01745, not 1, because one degree is only π/180≈0.01745\pi/180 \approx 0.01745 radians.

If a linearisation or a gradient step involving an angle behaves as if scaled by ~57x, a degree value slipped into a radian formula. Divide degrees by 57.29657.296 (that is 180/π180/\pi) before approximating.

The Quick Version

  • Degrees split a turn into 360; radians count radii of arc, with a full turn equal to 2π2\pi.
  • Convert with π/180\pi/180 going to radians and 180/π180/\pi coming back.
  • Arc length is simply s=rθs = r\theta when θ\theta is in radians.
  • 60 degrees is π/3\pi/3, about 1.047 radians; on radius 120 that cuts arc 125.66.
  • Libraries and calculus expect radians, so convert at the boundary and name the unit.
  • The small-angle shortcut sin⁡θ≈θ\sin \theta \approx \theta holds in radians only.