> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/guides/cloud-sync-google-drive-and-dropbox.md).

# Cloud Sync (Google Drive + Dropbox)

Configure Cloud Sync uploads for recordings using Google Drive and Dropbox

In Podcast Studio, Google Drive receives guest backups during recording. Dropbox uploads the host's finished recordings after recording stops. Wait for uploads to finish before closing the page.

## Google Drive

Google Drive uses an in-app OAuth flow.

1. Open the podcast studio and find **Recording settings**.
2. Click **Connect** next to **Google Drive**.
3. Complete the Google popup authorization (`drive.file` scope).
4. Confirm the status switches to **Connected**.
5. Click **Enable guest backup**. Each guest must accept the recording prompt; check that their backup is confirmed.

Uploads go to the `recordings` folder by default. To choose another folder:

`&recordfolder=YourFolderName`

## Dropbox

Connect Dropbox under **Recording settings** to upload the host's recordings after Stop.

1. Click **Connect** next to **Dropbox**.
2. Complete the Dropbox popup authorization.
3. Confirm the status switches to **Connected**.

The OAuth flow can remember the connection for future sessions.

## Manual Dropbox token fallback

If popup auth is blocked in a kiosk or constrained environment, you can still provide a token manually:

* Paste a token into the Dropbox field under **Recording settings**, or
* Use `&dropbox=YOUR_ACCESS_TOKEN`

Manual tokens can expire quickly, so OAuth is recommended for normal use.

## Related

{% content-ref url="/pages/GD22VCZck4ANSE56DLVO" %}
[\&gdrive](/advanced-settings/settings-parameters/and-gdrive.md)
{% endcontent-ref %}

{% content-ref url="/pages/TLXOv1LCYpqZKN5OUxtP" %}
[\&dropbox](/advanced-settings/settings-parameters/and-dropbox.md)
{% endcontent-ref %}

{% content-ref url="/pages/Rx73wZVNHnSDztNK81t6" %}
[Options to record streams](/guides/options-to-record-streams.md)
{% endcontent-ref %}


---

# 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.vdo.ninja/guides/cloud-sync-google-drive-and-dropbox.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.