Translate Gear Ratios, Module, DP & Tooth Count

If you are searching for how to translate gear ratios, how to translate module and diametral pitch, or how to preserve tooth count, pressure angle, sprocket size and reduction ratio across languages, the first rule is that these values describe mechanical relationships, not interchangeable labels. A 20-tooth gear, module 2 gear and 20 DP gear do not describe the same property, and a ratio written 4:1 must keep the same input-to-output direction.

Gear and sprocket translation matters in machinery manuals, gearbox specifications, automotive transmissions, robotics, bicycles, conveyors, industrial drives, spare-parts catalogues and engineering drawings. A target-language document can become mechanically wrong if driver and driven gears are swapped, if module is translated as diametral pitch without conversion, if tooth count is lost, or if a reduction ratio is inverted.

This guide explains how to translate gear ratios, module, diametral pitch and tooth-count specifications without changing mechanical meaning. It covers driver/driven relationships, 4:1 and 1:4 notation, module, DP, circular pitch, pressure angle, pitch diameter, spur and helical gears, bevel and worm gears, sprocket tooth counts, chain ratios, planetary sets and how to verify the final translation mathematically before publication.

Why gear-ratio translation must preserve mechanical relationships

A gear ratio is relational. It depends on which member is driving and which is driven, and on whether the source expresses speed ratio, torque multiplication, reduction ratio or tooth-count ratio.

Gear tooth geometry also uses different sizing systems. Module is a metric-style parameter related to pitch diameter per tooth, while diametral pitch expresses teeth per unit pitch diameter. They are reciprocally related through a conversion factor rather than being simple synonyms.

Tooth count, pressure angle, helix angle and pitch diameter are separate properties. A target description should not collapse them into one generic “gear size.”

The safest workflow is to preserve the source notation and member roles first, translate the explanatory terminology second, and treat any ratio inversion or module/DP conversion as a separately verified engineering calculation.

A reliable translation method

1. Identify driver and driven members

Mark which gear or sprocket is input and which is output before translating ratio language. Do not infer direction from the order of numbers alone.

2. Identify what the ratio represents

Determine whether the source gives speed ratio, reduction ratio, transmission ratio, torque ratio or tooth-count ratio. Preserve the source convention.

3. Protect tooth counts

Keep the number of teeth attached to the correct gear, pinion, sprocket or ring gear. Tooth count is an identifier of geometry and ratio.

4. Distinguish module from diametral pitch

Module and DP are different gear-sizing systems. Keep the source system unless a verified conversion is explicitly required.

5. Preserve pressure and helix angles

Angles affect meshing geometry. Keep pressure angle and helix angle separate from ratio or tooth-count data.

6. Keep gear type explicit

Spur, helical, bevel, worm and planetary systems use different geometry and terminology. Translate the gear type as part of the specification.

7. Treat chain and sprocket ratios separately

Sprocket tooth count determines chain-drive ratio, but sprockets are not simply gears with another name. Preserve the component type.

8. Verify mathematically and against drawings

Recalculate the ratio from tooth counts where possible and compare the target with the engineering drawing, gearbox datasheet or parts list.

Fifty recurring gear and sprocket translation problems

1. Simple gear ratio

This problem appears when two meshing gears define a speed relationship. A source expression such as 20T driving 60T can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

The translator should preserve the source notation and component identity first. Keep tooth counts with the correct gear or sprocket, retain module or DP as the original sizing system, and translate driver, driven, pinion, ring, sun, carrier and other role words consistently. Do not invert a ratio simply because the target language prefers a different word order.

For quality assurance, recalculate the simple ratio from tooth counts where possible and compare the target specification with the drawing or gearbox datasheet. If module is converted to diametral pitch, verify the formula and label the target value as a conversion. The target should describe the same rotational direction, speed change, torque relationship and meshing geometry as the source.

2. Reduction ratio

This problem appears when the output turns more slowly than the input. A source expression such as 3:1 reduction can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

3. Overdrive ratio

This problem appears when the output turns faster than the input. A source expression such as 0.8:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

4. Ratio direction

This problem appears when the same pair can be written in opposite order by different conventions. A source expression such as input:output 4:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

5. Driver gear

This problem appears when the input member is named explicitly. A source expression such as driver 20 teeth can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

6. Driven gear

This problem appears when the output member is named explicitly. A source expression such as driven 60 teeth can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

7. Pinion

This problem appears when the smaller gear has a specific role/name. A source expression such as 20T pinion can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

8. Gear wheel

This problem appears when the larger mating gear is identified. A source expression such as 60T gear can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

9. Tooth count

This problem appears when a drawing gives tooth number only. A source expression such as z = 32 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

10. Module

This problem appears when metric gear size is specified. A source expression such as module 2 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

11. Normal module

This problem appears when helical gear data uses normal module. A source expression such as mn = 2 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

12. Transverse module

This problem appears when helical gear data uses transverse module. A source expression such as mt = 2.13 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

13. Diametral pitch

This problem appears when inch-based gear sizing uses DP. A source expression such as 12 DP can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

14. Circular pitch

This problem appears when tooth spacing around the pitch circle is specified. A source expression such as circular pitch 6.28 mm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

15. Pitch diameter

This problem appears when gear size is described by the pitch circle. A source expression such as pitch diameter 80 mm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

16. Outside diameter

This problem appears when tip diameter is listed separately. A source expression such as OD 84 mm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

17. Root diameter

This problem appears when tooth-root geometry is listed. A source expression such as root diameter can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

18. Pressure angle

This problem appears when tooth profile angle is specified. A source expression such as 20° pressure angle can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

19. Helix angle

This problem appears when helical gear teeth have an angle. A source expression such as 15° helix angle can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

20. Spur gear

This problem appears when straight-tooth cylindrical gear type is named. A source expression such as spur gear can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

21. Helical gear

This problem appears when angled-tooth cylindrical gear type is named. A source expression such as helical gear can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

22. Bevel gear

This problem appears when intersecting-shaft gear type is named. A source expression such as bevel gear can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

23. Worm gear

This problem appears when worm/wheel system has a distinct ratio structure. A source expression such as worm gear 40:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

24. Worm starts

This problem appears when ratio depends on wheel teeth and worm starts. A source expression such as 2-start worm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

25. Planetary sun gear

This problem appears when the central gear has a tooth count. A source expression such as sun 24T can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

26. Planetary ring gear

This problem appears when the outer internal gear has a tooth count. A source expression such as ring 72T can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

27. Planet carrier

This problem appears when the carrier may be input or output. A source expression such as carrier output can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

28. Planet gear

This problem appears when planet gears participate in the set geometry. A source expression such as planet 24T can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

29. Sprocket ratio

This problem appears when chain drive uses tooth counts. A source expression such as 15T / 45T sprockets can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

30. Bicycle chainring

This problem appears when front sprocket is described by tooth count. A source expression such as 50T chainring can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

31. Bicycle cassette sprocket

This problem appears when rear sprocket tooth count changes ratio. A source expression such as 25T sprocket can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

32. Timing belt pulley

This problem appears when toothed pulley count is specified. A source expression such as 20T pulley can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

33. Pulley ratio

This problem appears when belt drive may use diameter instead of teeth. A source expression such as 100 mm / 200 mm pulleys can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

34. Gearbox stage

This problem appears when a multi-stage gearbox has separate ratios. A source expression such as stage 1: 3:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

35. Overall ratio

This problem appears when multiple stages combine into a total reduction. A source expression such as overall 12:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

36. Final drive ratio

This problem appears when vehicle driveline has a final reduction. A source expression such as final drive 4.10:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

37. Transmission gear ratio

This problem appears when individual gearbox gears have ratios. A source expression such as 2nd gear 1.95:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

38. Differential ratio

This problem appears when axle gearing has a fixed ratio. A source expression such as 3.73:1 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

39. Rack and pinion

This problem appears when rotary-to-linear motion uses tooth pitch and pinion size. A source expression such as module 1 rack can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

40. Internal gear

This problem appears when ring gear teeth mesh internally. A source expression such as internal gear 72T can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

41. Gear pair backlash

This problem appears when clearance between teeth is specified. A source expression such as backlash 0.10 mm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

42. Center distance

This problem appears when gear centers have a fixed spacing. A source expression such as center distance 100 mm can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

43. Profile shift

This problem appears when gear correction coefficient is specified. A source expression such as x = +0.3 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

44. Gear quality grade

This problem appears when manufacturing accuracy grade is listed. A source expression such as quality grade can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

45. Torque multiplication

This problem appears when ratio is described through output torque increase. A source expression such as 3× torque can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

46. Speed reduction

This problem appears when ratio is described through output speed decrease. A source expression such as output speed one third of input can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

47. Reverse direction

This problem appears when external gears reverse rotational direction. A source expression such as opposite rotation can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

48. Same direction stage

This problem appears when idler gears affect direction but not simple magnitude ratio. A source expression such as idler gear present can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

49. Compound gear train

This problem appears when two gears share a shaft in a multi-stage train. A source expression such as compound train can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

50. Ratio from teeth

This problem appears when the target text derives ratio from tooth counts. A source expression such as 60/20 = 3 can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

51. Module-DP conversion

This problem appears when the target document wants both sizing systems. A source expression such as module 2 ≈ 12.7 DP can encode tooth geometry, component role, speed relationship, torque relationship or a sizing system. If the target text keeps the number but changes the role or direction, the resulting mechanism can be described incorrectly.

Common failure modes

1. Inverting the ratio

A 4:1 reduction is not the same as 1:4 when input/output convention is fixed.

2. Swapping driver and driven gears

The tooth counts may remain the same while the speed and torque interpretation reverses.

3. Treating module and DP as synonyms

They use different definitions and require a reciprocal conversion relationship.

4. Dropping the T/tooth-count marker

A bare number can become ambiguous if the context contains diameters, modules or ratio values.

5. Ignoring pressure angle

Gears with different pressure angles may not mesh correctly even if tooth count and module match.

6. Ignoring helix angle or hand

Helical gear geometry depends on angle and direction as well as module and tooth count.

7. Combining stage ratios incorrectly

Multi-stage gearbox ratios multiply according to the actual train; they should not be added casually.

8. Treating sprockets as ordinary gears

Chain sprockets have tooth-count ratios but different geometry and terminology from meshing gears.

Worked practice

Practice 1: Simple reduction

Situation: A 20T driver meshes with a 60T driven gear.

Reasoning: Keep the driver/driven roles and verify the resulting 3:1 reduction using the source convention.

Practice 2: Module specification

Situation: A spur gear is module 2, 20° pressure angle, 30 teeth.

Reasoning: Preserve all three properties; do not reduce the description to ‘gear size 2’.

Practice 3: DP specification

Situation: A US drawing calls for 12 DP.

Reasoning: Keep 12 DP. Add a module equivalent only if the target document explicitly needs one and verify the calculation.

Practice 4: Worm gear

Situation: A 1-start worm drives a 40-tooth wheel.

Reasoning: Preserve worm-start count and wheel teeth because both determine ratio.

Practice 5: Planetary set

Situation: Sun, ring and carrier roles are specified.

Reasoning: Keep each member’s role and tooth count aligned; planetary ratios depend on which member is fixed, input and output.

Practice 6: Chain drive

Situation: A 15T front sprocket drives a 45T rear sprocket.

Reasoning: Translate sprocket terminology while preserving tooth counts and drive direction.

Practice 7: Automotive final drive

Situation: The source states 4.10:1 final drive.

Reasoning: Keep the ratio and its driveline meaning; do not rewrite it as a generic gearbox ratio.

Practice 8: Compound gearbox

Situation: Two stages are listed separately with an overall ratio.

Reasoning: Preserve stage ratios and independently verify the stated total if calculation is part of QA.

Drawings, gear calculators and AI

Engineering drawings, gearbox catalogues, machine manuals and parts lists are the strongest sources for gear translation. They show tooth counts, module/DP, angles, center distances and member roles in context.

Gear calculators can verify simple tooth-count ratios and module/DP conversions, but they do not decide which member is input or output. That role must come from the mechanism or source documentation.

AI can explain gear terminology, but it may invert ratios or oversimplify planetary systems if the fixed/input/output members are not specified. Provide the mechanism roles explicitly and verify results independently.

How this fits the wider eduKate translation system

Gear translation combines ratios, geometry, identifiers and role relationships. The broader method is developed in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while relational language, comparison and technical noun phrases connect to How English Works.

FAQ

Is a 4:1 ratio the same as 1:4?

No, not when the source defines which side is input and which is output.

What does T mean in gear descriptions?

It commonly denotes tooth count, such as 20T for twenty teeth.

Is module the same as diametral pitch?

No. They are different gear-sizing systems related by conversion.

Can I convert module to DP?

Yes mathematically when appropriate, but preserve the source system and verify the conversion.

Does an idler gear change the ratio?

In a simple train it can change rotational direction without changing the magnitude ratio between first and last gears, but check the actual arrangement.

Do pressure angle and helix angle matter in translation?

Yes. They are part of gear geometry and compatibility.

Can sprocket tooth counts be translated as gear ratios?

You can calculate a drive ratio from them, but keep sprocket terminology and chain-drive context.

Are planetary gear ratios simple tooth-count ratios?

They depend on which member is fixed, input and output, so the role structure must be preserved.

Can AI verify a gearbox ratio?

It can assist with calculation, but the member roles and train layout must be confirmed from the source.

What is the simplest rule?

Protect tooth counts, member roles, ratio direction and gear-sizing system as one mechanical relationship.

Final checklist

Are driver and driven members identified correctly?
Is the ratio direction preserved?
Are tooth counts attached to the correct components?
Are module and diametral pitch kept distinct?
Are pressure and helix angles retained?
Is the gear or sprocket type preserved?
Are planetary member roles explicit?
Are stage and overall ratios kept separate?
If a conversion was made, was it mathematically verified?
Would the target mechanism produce the same speed, torque and direction relationship as the source?

Gear-ratio translation succeeds when the target reader reconstructs the same mechanical relationship: the same tooth counts, the same input/output roles, the same sizing system and the same speed and torque behavior. Protect ratio direction, preserve gear geometry and verify every derived or converted value before publication.

Translate | Gear Ratios, Module, Diametral Pitch, Tooth Count and Sprockets — Preserve Mechanical Relationships Across Languages