> For the complete documentation index, see [llms.txt](https://docs.gyroflow.xyz/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gyroflow.xyz/app/getting-started/supported-cameras.md).
# Supported Cameras
Gyroflow supports wide variety of cameras. You can find links to detailed camera guides here
{% hint style="info" %}
**What about Nikon, Panasonic, Fujifilm, Pentax, etc.?**\
Gyroflow supports all cameras that record gyroscope data. Consumer cameras such as those from Nikon, Panasonic, Fujifilm, Pentax, etc. don't record gyro data internally, and therefore cannot be used with Gyroflow.\
\
Gyroflow requires the camera to have a hardware gyroscope and to record it together with the video file - so there's nothing we can do on the software side, if the camera didn't provide the gyro data. This is not something Gyroflow developers can fix.
You can try to reach the camera manufacturer and express interest in adding gyro data. If they see enough interest, they may add that functionality to the camera.\
\
However, it is possible to use an external gyro source with cameras that don't record gyro data internally. You can learn more [here](/app/advanced-usage/using-external-gyro-source.md).
{% endhint %}
---
# 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://docs.gyroflow.xyz/app/getting-started/supported-cameras.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.
