# Automate sequential naming and export clips from a timeline.

### Using DaVinci Resolve

DaVinci Resolve is highly recommended for easily exporting individual clips and sequential naming simultaneously.&#x20;

Moreover, it's free.

First, gather all the clips you want to export as individual clips to fill the video grid and arrange them in a timeline. Then follow these steps:

1. Navigate to the **Deliver page**;
2. Choose the export location at "**Location**";
3. Under the Render option, select "**Individual clips**";&#x20;
4. Set your video compression parameters like resolution, format, codec etc. in the **Video** tab.&#x20;
5. In the **File** tab, ensure your filename uses "**Custom name**";
6. Enter "**video**" then a "**%**" symbol in the "**Custom name**" field. Continue typing until "**Timeline Index**" appears, then select it;
7. **Uncheck** "**Add source frame count to filename**";
8. Lastly, "**Add to the Render Queue**" and "**Render all**" in the right-hand render queue.

<figure><img src="https://3815411331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyVilOHwONIDkwMzNzM75%2Fuploads%2F3VnaCB5T8DCjQTNlWKWX%2FScreenshot%202024-01-11%20at%2016.03.14.png?alt=media&#x26;token=1046dbb3-108a-406a-906e-d44727a37dac" alt="" width="375"><figcaption><p>Your render settings under the File tab should look like this.</p></figcaption></figure>

**Pros**:

* You can edit, export, and sequentially name all in one place simultaneously.
* Effects you applied can be kept into the exports.

**Cons**:

* The scene detection tool, which automatically slices timelines made from longer film clips based on scene change, is only available in the paid Studio version of the software.

### Using Final Cut Pro

Don't use Final Cut Pro for this project. It doesn't provide an easy solution for this specific task.

### Using Adobe Premiere Pro

Premiere Pro also lacks a built-in feature for this task, but some online creators have suggested using **Render and Replace** as an alternative.

Check out these tutorials:

{% embed url="<https://www.youtube.com/watch?v=mJi_G3waGmg>" %}

{% embed url="<https://www.youtube.com/watch?v=e8LYA4INBKQ>" %}

**Pros:**

* As of 2023, the Premiere Pro workflow, due to its popularity, sets the standard and is likely more familiar to you;
* Do not need to pay extra for scene detections;
* Effects you applied can be kept into the exports.

**Cons:**

* Speaking from my understanding now, you cannot set custom names and the pixel amount to the exported clips. (Add the Handbrake transcoding steps below into your workflow.)

### Using Handbrake for Batch Resizing(Transcoding) and Renaming&#x20;

If you work with ready-made files or export with Premiere Pro's Render and Replace option, the Handbrake software allows you to conveniently resize and rename simultaneously.

1. Click "**Open Source**," and in the file explorer, choose the folder that contains all your files or manually selecting your videos while holding down "Shift";
2. Adjust dimension, framerate, codec, and format as needed;
3. In the "Save as" text input at the bottom, enter "**video%d.mp4**";
4. Choose preferred output directory;
5. Click the **down arrow** next to "Add to Queue" to select "**Add All Titles to Queue**";
6. Hit "Start".

{% hint style="info" %}
Handbrake automatically imports multiple files in alphanumeric order from a->z and 0->9. You can't rearrange the order after having added the source.&#x20;

So, if the default filename order doesn't align with your desired final result, you'll need to manually adjust it a little before feeding them into Handbrake.
{% endhint %}

Have fun with automation!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://quan-1.gitbook.io/interactive-video-grid/automate-sequential-naming-and-export-clips-from-a-timeline..md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
