How to Organize TikTok Video Files for Automated Publishing

An automation should receive one exact approved video file. If the folder contains final.mp4, final-new.mp4, and final-really-new.mp4, the person preparing the post has to guess which one the creator reviewed.

Organize TikTok production files so each video has a stable identity, each revision keeps its own version, and approval points to a particular export and caption. Choose folder names your team understands, and use them consistently.

The structure below belongs to your own storage and production process. It does not describe a built-in Groniz media library or approval system.

Give the video a permanent ID

Imagine a creator selling a downloadable garden-planning workbook. Video GP014 demonstrates entering a planting date in the workbook. Its hook may change during editing, but the ID stays GP014.

Use that ID in the brief, shot manifest, editor handoff, and publication record. Keep the product version separate: GP014 can demonstrate workbook version 2 while the video export itself is revision 3.

A name such as GP014-planting-date-v003.mp4 identifies the video and export revision. Record its approval separately, with a reference to this exact file.

If recording takes are still difficult to identify, start with the shot manifest in batch recording TikTok videos. Record the take selection there so the editor knows which footage to use.

Separate sources, edits, exports, and approved material

Use a structure like this for each video:

tiktok/
  GP014-planting-date/
    brief.md
    sources/
      GP014-S01-take01.mov
      GP014-S02-take02.mov
    edits/
      GP014-project-v001.editor
      GP014-project-v002.editor
    exports/
      GP014-planting-date-v001.mp4
      GP014-planting-date-v002.mp4
      GP014-planting-date-v003.mp4
    captions/
      GP014-caption-v001.txt
      GP014-caption-v002.txt
    approved/
      GP014-planting-date-v003.mp4
      GP014-caption-v002.txt
      approval.json
    manifest.csv

The .editor extension here stands for your editor's actual project format. This is an illustrative folder tree, not executable publishing code.

Keep captured footage in sources and project revisions in edits. Rendered candidates go in exports; copy only files cleared for delivery into approved, together with the review record.

If you copy an export into approved, verify that the copy matches the reviewed export. A checksum can establish byte-for-byte identity; it cannot establish that the content is accurate or suitable. Record both the review and the identity check.

Make versions immutable

Once someone reviews version 3, preserve version 3. A spelling correction creates version 4 even if it changes only one frame. The caption follows the same rule: a revised price, destination, or sentence creates a new caption version.

In the workbook example, the reviewer notices that GP014 version 2 shows an old column label. The editor exports version 3 using the current workbook. The reviewer approves version 3 with caption version 2. Both earlier exports remain clearly separate from the approved pair.

If the creator later changes the spoken instruction, the editor creates version 4. It requires a new review before it can replace version 3 in a delivery handoff. Overwriting version 3 would make the old approval ambiguous.

A storage service may offer locking or version history. Use those controls if available and write down the rule for everyone handling files: keep reviewed files unchanged and give each replacement a new identifier.

Keep a manifest the person publishing can follow

The manifest records what each file contains and whether someone has approved it. Keep one row per export candidate, or use another format that preserves the same information.

Video ID:
Buyer question:
Product version shown:
Source take references:
Edit project reference:
Export version and exact path:
Export checksum:
Caption version and exact path:
Caption checksum:
Review decision and reviewer:
Review timestamp:
Approved pair reference:
Supersedes export version:
Reason for replacement:
Delivery record reference, when available:

Do not put account credentials into this document. The publishing account and its delivery settings belong in a controlled handoff; authentication belongs in the delivery tool's supported authentication flow.

Before someone prepares a file for delivery, they should be able to confirm from the manifest which export was approved, which caption belongs to it, and whether a newer decision has superseded that pair. Resolve any missing or conflicting details before handing off that video.

Preserve the upload reference without confusing it with approval

For delivery through Groniz, media is uploaded before use, and the returned .path is used in the delivery request. Record that reference beside the exact approved local export it represents. A local filename and an uploaded media reference are different identifiers.

If you upload version 4, do not silently reuse version 3's stored upload reference. Associate each upload with its source file and review record. Upload completion also does not establish that a post was published.

Groniz Connectors handles supported delivery operations. It does not create these folders, edit the videos, or approve their contents. Discover the connected account's current capabilities before building the final delivery request.

The creator measures paid workbook purchases in checkout records. The manifest identifies which approved video was delivered, but attributing a purchase to that video requires separate evidence. Keep that distinction in your TikTok automation and owned-product workflow.

Once the approved pair and manifest agree, open Groniz Connectors to prepare delivery using the correct uploaded media reference.