> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vturb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update turbo

> Turn accelerated playback on and set its rate with a two-key patch.

Turbo speeds the video up: with it on, playback runs at the configured rate
instead of 1.0×. A merge-patch can flip it on and choose that rate.

This is a [merge-patch](/guides/merge-patch): send only the keys you want to
change and everything else keeps its stored value.

## Turn turbo on at 1.5×

<CodeGroup>
  ```bash cURL theme={null}
  curl -X PATCH https://api.vturb.com/v1/videos/{id} \
    -H "Authorization: Bearer vt_..." \
    -H "Content-Type: application/json" \
    -d '{ "turbo": { "enabled": true, "speed": 1.5 } }'
  ```

  ```json Body theme={null}
  {
    "turbo": {
      "enabled": true,
      "speed": 1.5
    }
  }
  ```
</CodeGroup>

## The keys

| Key       | Type    | Writes                                      |
| --------- | ------- | ------------------------------------------- |
| `enabled` | boolean | Turns turbo on or off                       |
| `speed`   | number  | Playback rate while turbo is on, e.g. `1.5` |

## What you'll read back but can't write

`GET` also returns `mode`, and during an A/B experiment `speed_start`,
`speed_end` and `winner`. Those are set by the experiment: sending them in
a patch is silently ignored, not rejected. And note that a crowned `winner`
outranks the `speed` you configure — the player serves the winner's rate until
the experiment is cleared.