Snitt
Download

Your editing style

Importing published videos

Point Snitt at videos from your own channel so it can learn how you edit.

This page covers adding published videos to a profile — by file or by YouTube link — how many to add, what Snitt learns from them, and which files it refuses.

Import only videos from your own channel. These are finished, published edits; Snitt reads them to learn how they were cut. Our terms ask you to confirm you own what you import, which is the case when the channel is yours.

Add videos to a profile

  1. Select the profile first

    Open Style profiles and click the profile in the list on the left. Videos are always added to the selected profile — the drop target says which one by name.

  2. Drop the files in, or browse for them

    Drag published videos onto the drop target, or click Add videos… and pick them. Any video file your Mac can decode works.

  3. Or paste a link from your own channel

    Click Add from YouTube… and paste a watch, youtu.be or Shorts link, then click Download. Snitt fetches the video into its own storage and imports it, and picks up the publish date that way.

  4. Watch the rows

    Each video runs on its own and reports Queued, Analyzing, then Analyzed. You can keep working in the app, and you can add the next one before the first has finished.

  5. Add a few more

    The profile is rebuilt from scratch after every import, so the numbers get better as videos land.

How many videos to start with

Start with a handful — five to ten typical videos is a good first pass. Pick ones that represent how you normally cut, not the outliers.

More videos make the profile more confident. One video shows what you did once; three or more shows how much you normally vary.

Recent videos count for more than old ones, so a channel that changed style over the years is still described as it is cut today.

What Snitt learns from them

Only how the videos are edited — your style, not your content. Sponsor reads are left out.

Nothing about the topic is used, and nothing from a published video is copied into a new one. See what we learned.

Files Snitt refuses

Every video is checked all the way through as it is analysed, so the verdict covers the whole file rather than a sample of it.

  • A badly damaged file is rejected at import. The message on the row says what Snitt found. Re-export it from your editor, or download a fresh copy, and add it again.
  • A file with minor damage is accepted, with a note on its row. Older re-encodes often produce harmless decoder complaints, which alone are not a reason to reject a file.
  • A file damaged enough to matter but not enough to refuse is used, and what Snitt learned from it is marked approximate.

A file that opens fine in a player can still be damaged, which is why Snitt checks the whole file.

What it costs

Importing a video is a job like any other, so it uses minutes from your balance in proportion to the video’s length. Working through a back catalogue is a one-time cost; after that, only new uploads add to it.

How your footage is handled is covered in our privacy policy.

If something goes wrong

The row says the file is unreadable. It is damaged. Re-export it from your editor, or download a fresh copy, then add it again.

“That doesn’t look like a YouTube video link.” Snitt takes watch, youtu.be and Shorts links to a single video. Channel, playlist and other links are not videos.

“That video has been removed from YouTube.” Nothing to import. Use a local copy of the file instead.

“Couldn’t reach YouTube.” A network problem. Check the connection and click Add from YouTube… again.

YouTube import is not available in this copy of Snitt. The downloader is missing from the app bundle. Reinstall Snitt from the download page, or add the video as a file.

A row says Paused. The import stopped at a step that could not finish. Nothing is lost. Click Resume and it picks up where it stopped rather than starting over.

A row says Failed. Click Retry. If it fails again on the same file, the file itself is the likely problem — see the decode cases above.