> 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/advanced-usage/color-differences.md).

# Color Differences

If the colors look different after exporting from Gyroflow, in most cases the pixels didn't change: a player or video editor just interprets the color range or the gamma of the file differently.

## What Gyroflow does

Gyroflow processes the video directly in its original YUV format, without converting the colors. The exported file gets the same color metadata as the original: the color range, the color matrix, the transfer curve (gamma) and the color primaries.

A few encoders don't store all of it:

* GPU encoding on macOS (VideoToolbox) doesn't write the transfer curve.
* ProRes encoded on the GPU on macOS from 8-bit 4:2:0 video is always limited range (Gyroflow converts the pixels to match, to work around an encoder bug).
* The H.264/H.265 GPU encoder on Intel Macs ignores the requested color range.

## Color range

The color range is either **Full** (0-255, also called JPEG or Data levels) or **Limited** (16-235, also called MPEG or Video levels), and it's stored in the file metadata. Players, video editors and websites don't always read it the same way:

* Limited range shown as full looks washed out (grey blacks, dull whites).
* Full range shown as limited looks too contrasty (crushed blacks, clipped whites).

In DaVinci Resolve, you can change it in `Clip Attributes -> Data Levels` (Auto, Video or Full).

## Gamma

The transfer curve (gamma) can also be interpreted differently, for example by QuickTime on macOS, or after uploading to YouTube. This happens with any video, not only with files from Gyroflow.

## How to find the cause

Your file can look the same or different at every stage: the original file, the export from Gyroflow, played in VLC, imported in your video editor, exported from the editor, uploaded to YouTube etc. Compare them in the same player, and change one thing at a time. There's no single rule, so find a workflow that works for your setup.

Read more about color range:

* [Color Space and Color Range](https://cinelerra-gg.org/download/CinelerraGG_Manual/Color_Space_Color_Range_Aff.html) (Cinelerra-GG manual)
* [RGB Full vs. Limited](https://referencehometheater.com/2014/commentary/rgb-full-vs-limited/)
* [Data Levels Settings and Conversions](https://coloraggio.github.io/davinci-resolve-manuals/12.5_Manual/6.pdf) (DaVinci Resolve manual)

## Avoiding it altogether

Use one of the [video editor plugins](https://docs.gyroflow.xyz/app/video-editor-plugins/general-plugin-workflow.md). The editor then reads the original file and applies the stabilization itself, so there's no extra file whose colors could be interpreted differently.


---

# 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/advanced-usage/color-differences.md?ask=<question>&goal=<user_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.
