# One-off exports

{% hint style="info" %}
One-off exports are included on paid [Shadow Fork plans](https://www.shadow.xyz/pricing).
{% endhint %}

One-off exports allow you to export data to a destination of your choice for a specified block range.

## Steps

1. **Choose your data:** Export shadow and/or mainnet data (coming soon), and specify which contracts and events you want to export.
2. **Choose your destination:** Export your data to Dune, GCS, or S3 (coming soon).
3. **Choose your settings:** Specify the block range you want to export over, the file format (CSV or Parquet), and how to partition the data (daily, hourly, or no partitioning).

<figure><img src="https://4112099338-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS7wZ4G2hJbxyJhrQE8Kz%2Fuploads%2FgEMzBWw559kDG14a4HWh%2Fimage.png?alt=media&#x26;token=e39ff77a-096a-4bb9-8d23-0be2167ff33b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If you choose to export shadow data, you’ll only be able to select events from contract addresses that you have shadowed (e.g. deployed modifications to).\
\
If you shadowed the implementation of a proxy contract, you’ll need to perform a “no-op deploy” on the proxy contract by hitting “Compile > Deploy” in the editor without making any shadow changes. We’re working on a better experience for this!
{% endhint %}