> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/transmitting-power/gears/gear-ratios.md).
# Gear Ratios
A gear ratio is the relationship between the sizes of two gears. If a smaller driving gear turns a larger driven gear, the larger gear rotates more slowly but with greater torque.
For example, if a driving gear has 10 teeth and the driven gear has 20 teeth, the ratio is 2:1, meaning the smaller gear must complete two full rotations for the larger gear to rotate once.
Gear ratios in *FIRST* Tech Challenge are crucial for optimizing speed and torque, depending on the task at hand.
Increasing Speed
If you use a higher gear ratio (2:1, for example), the output gear spins faster than the input gear, while lowering torque. This is particularly useful for applications such as active intake, flywheel, or turret systems.
Increasing Torque
A lower gear ratio (1:2, for example) means the output gear rotates more slowly but with greater force. This is ideal for lifting mechanisms, drivetrains, or linear extension.
To optimize efficiency, ensure that torque and speed are balanced; having excess torque on a wrist joint could mean wasted force, so gearing it up for extra speed can improve movement while maintaining control. Always match the gear ratio to the actual load and motion requirements to avoid inefficiencies that drain power or limit performance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.ftcwiki.org/transmitting-power/gears/gear-ratios.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
