Make an edit pack

What goes in the zip

my-edit/
  edit.json        what plays where (you write it)
  clips/           your finished MP4 clips, any file names
    scene one.mp4
    cold open.mp4

1. Find the episode and copy its details

Open the show in the catalog, find the episode, and press Copy episode details (signed in as a creator). In Chrome you can also open the episode on Prime Video and choose Copy episode details in the Seamless Scene player menu.

Paste what it copies into edit.json as the "episode" entry. It holds the episode's Prime Video id (the GTI) and its exact length, so never type those by hand: the wrong GTI is the usual reason a local edit is never offered.

2. Mark the scene times

You need the extension's Creator edition (a ZIP for approved creators on the install page); the Chrome Web Store edition has no side panel.

On Prime Video, open the extension's Creator side panel, pause on the first frame you change, and press Copy beside the time. Paste it as the scene's start (or at for an insert). Do the same for end.

3. Make the clips

Render each finished clip and put it in the clips folder. Any file name works.

The rules are below. If a render doesn't follow them, convert it with ffmpeg.

• MP4 with one H.264 video stream (yuv420p) and one AAC audio stream, standard dynamic range.
• Between 1.5 and 120 seconds for a local edit (extension 0.64.3 or later); between 5 and 120 seconds to submit. Edits from the builder need clips of 5 s or more; 1.5 s clips play only as local packs made outside the builder.
• Even width and height, from 320×180 to 4096×2160.
• At most 250 MB each, so the same pack also submits (a local edit allows up to 512 MB).

ffmpeg -i "my render.mov" -c:v libx264 -pix_fmt yuv420p -crf 18 -preset slow -c:a aac -b:a 192k -movflags +faststart "clips/scene one.mp4"

4. Write edit.json

Start from the example file, then fill in the fields in the table below. The importer measures each clip, so you never write hashes, sizes or durations.

Or let the extension write it: in the Creator side panel, fill in the Listing section (the same settings as the table) and press Save as edit pack. It saves edit.json with the episode, your marked scenes and the listing; add the clips yourself.

Set every publication setting yourself: nothing is assumed. A pack without them still plays on your stream; the builder asks for whatever is missing before you can submit.

Publication settings, one to one

Nothing is filled in for you. A setting that is missing or breaks its rule shows in the builder as “missing from edit.json”, and the edit can’t be submitted until it is set there. spoilers, synthetic_media, real_person_likeness, warnings and poster.jpg are ignored if present: use tags to describe the edit.

Each scene

5. Zip the folder

Windows: right-click the folder, then Send to → Compressed (zipped) folder.

macOS: right-click the folder, then Compress.

For very large folders Windows may use Deflate64, which browsers can't read. Then zip with 7-Zip and choose Deflate or Store.

The .zip name is fine; you don't need to rename it. Don't rename a zip that isn't an edit pack to .ss: the extension converts a real edit pack into a .ss when you add it.

6. Play it on your own stream

Open the extension's settings, go to Local and choose Add a local edit, then pick the zip. It's checked once and kept in the extension.

Open the episode on Prime Video: the edit is offered as Local: <your title>.

7. Submit it to the catalog

On the website, go to My edits → Import an edit pack and choose (or drop) the same zip.

The builder opens with a Ready to submit panel: episode, clips, listing and quality. Any setting edit.json left out or got wrong is listed there as missing from edit.json; Fix → takes you to it in the Listing form. Set each one, then press Submit for review.

For a new version, raise revision in edit.json and import again: the builder offers Update <name> as version N.

When something is refused

More help: Troubleshooting.