[{"_1":2,"_186":-5,"_187":-5},"loaderData",{"_3":4},"routes/tag.$slug",{"_5":6,"_106":113,"_168":33,"_169":33,"_170":53,"_171":172},"posts",[7,123],{"_8":9,"_10":11,"_12":13,"_14":-5,"_15":-5,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":31,"_32":33,"_34":9,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_65":66,"_75":76,"_102":103},"id",3,"slug","how-loud-should-a-short-form-video-be","locale","en","translationOfId","translationOfKey","title","How Loud Should a Short-Form Video Be?","excerpt","Learn LUFS in plain English, balance voice and music, compare a quiet upload on your phone, and set a practical target before you post.","content","

Use -14 LUFS integrated as a practical working target for a finished short-form mix, with true peak kept below clipping. It is not an official TikTok, Instagram, or YouTube Shorts upload requirement. Start with a clear voice, lower music under speech, check the export on the same phone volume, and resist boosting a quiet mix until it distorts.

\n\n

\"Angled — Check loudness on the finished file, not only on the timeline.

\n\n

Audio levels are easy to judge badly. A waveform can look tall while the words feel weak, or a mix can sound fine in your editor and turn quiet beside the next video. You need one target, a clean voice-to-music balance, and a check on the file viewers will actually hear.

\n\n

How loud should a TikTok, Reel, or Short be?

\n\n

If you are asking how loud a TikTok video should be, or looking for LUFS for Instagram Reels, start with -14 LUFS integrated. That is the target most creators and tools work to for a finished social mix. It gives you a repeatable starting point without promising identical playback on every phone.

\n\n

TikTok, Instagram, and YouTube Shorts do not publish one official upload loudness specification you can rely on here. Treat -14 LUFS as a working target for normalizing audio for social media, not a rule a platform requires. Then listen. A ten-second phone check catches problems a number cannot.

\n\n

Why your video sounds quiet next to the one before it

\n\n

The feed puts unlike mixes next to each other. One creator may push every word into a limiter while the next leaves more space around the voice. Your phone volume stays fixed, so the quieter average mix feels wrong even when its peaks look healthy.

\n\n

Music creates the same illusion. A bright, dense song grabs attention at a lower meter reading than a soft voice over a sparse bed. Silence, long pauses, and a voice recorded far from the phone also lower the average. Find the quiet part before changing the master.

\n\n

When one video goes to several feeds, keep the audio decision in the original export. Our guide to repurposing one script for TikTok, Reels, and Shorts covers the changes around the video, not repeated re-uploads.

\n\n

Peak volume and perceived loudness are different

\n\n

Peak is the tallest moment

\n\n

A peak meter answers one question: what was the loudest instant? A clap, plosive, laugh, or music hit can top the meter while the sentence sits lower. If it reaches 0 dBFS, the file can clip. Lowering the mix fixes the peak, not the quiet words.

\n\n

Perceived loudness is the running experience

\n\n

Perceived loudness follows what you hear across time. Compression and limiting reduce the gap between quiet and loud moments, making a track feel louder without raising its highest peak. Push too far and the voice pumps, breaths stand out, and consonants lose shape.

\n\n

True peak checks for peaks between digital samples when a file is converted or played. A true-peak ceiling gives them room. That is why a mix can avoid obvious clipped samples in the editor and still crackle after encoding.

\n\n

LUFS without the audio-engineering lecture

\n\n

LUFS measures loudness over time. The meter applies a hearing-weighted filter and averages the result, so it is closer to listening experience than a sample peak. ITU-R BS.1770 defines the measurement approach. EBU R 128 is a related framework used in broadcast and post-production tools.

\n\n

Integrated LUFS considers the whole program, from first audio frame to last. A quiet intro or long pause affects the number. Short-term and momentary readings show smaller windows, useful for finding a loud section but not for describing the whole upload.

\n\n

For short-form social video and many streaming workflows, -14 LUFS integrated is a sensible working target. It is not magic or a platform pass mark. A quiet opening can feel soft at -14, while a dense mix can feel tiring at the same reading. Use the number to get close, then listen.

\n\n

Why chasing louder backfires

\n\n

The fastest way to make a mix louder is to remove movement. A limiter catches peaks and turns the rest up, but if it works on every syllable, speech rises and falls with it. That pumping is obvious when music sits under a voice.

\n\n

More level exposes distortion. Consonants flatten, music loses punch, and the video gets tiring. Some platforms may turn loud uploads down during playback normalization, so the pushed file can end up no louder than a restrained one, with less headroom and more damage.

\n\n

Leave room for conversion and playback. A clean mix that lands near the working target is easier to hear than a clipped mix that wins the meter for half a second.

\n\n

Balance the voice and music before you master

\n\n

In a talking-head video, the voice is the message. Mute the music and make the spoken line clear on a phone speaker. Bring music up until it adds energy, then lower it one step. If you have to work to catch a word, music is too loud.

\n\n

Use ducking when music stays present. Pull it down as speech starts, let it rise during a pause, and avoid an instant jump on every word. A slow release sounds more natural than music that vanishes and returns like a switch.

\n\n

Check the loudest spoken line, quietest useful line, and music-only moment. If music has vocals, treat it as a second speaker and lower it further. Fix competing tracks before adding master gain.

\n\n

A no-meter loudness check you can do on your phone

\n\n

You can get a useful answer without knowing the LUFS reading. Use a reference video with a similar voice, pace, and amount of music. Our guide to making UGC videos on your phone shows a phone-first setup you can repeat before judging the audio.

\n\n

Put your reference video and your export on the same phone.
Set the phone to a comfortable volume and do not touch it during the comparison.
Listen to the first few seconds, one spoken sentence, and the loudest section of each video.
Switch between the two without looking at the volume control.
Repeat once through the phone speaker and once through the headphones you normally use.

\n\n

Write down what you hear. \"The voice is buried under the music\" points to ducking. \"The whole file is soft\" points to gain or low average level. \"The loud part crackles\" points to clipping or a hard limiter. The note tells you what to change.

\n\n

What to do when your desktop editor has a loudness meter

\n\n

A meter makes the check repeatable if you measure the right signal. Put it on the final mix bus after voice, music, effects, and limiter. Measure the entire video, not just the loudest sentence.

\n\n

Play the complete mix and read the integrated LUFS result.
Use -14 LUFS integrated as your working target for the social export.
Watch true peak and keep the ceiling below clipping, with room for encoding.
Listen for pumping, harsh consonants, and buried words while the meter runs.
Export the file, then measure that saved file again instead of trusting the timeline reading.

\n\n

Choosing an editor? Our guide on how to choose a video editor for UGC videos helps you score the checks that happen after creative decisions. Loudness is one of those final checks, and it should not leave you guessing which version reached the export folder.

\n\n

Fix a quiet upload without making it worse

\n\n

First compare the uploaded post with the saved export on the same phone, volume, and speaker. If the export is quiet, inspect the voice, ducking, and integrated reading. If the export is clear but the post is not, check the uploaded file and playback path before changing the master.

\n\n

Do not raise the master until you know whether the voice or the music is quiet.
Do not judge from the waveform height alone.
Do not compare a phone speaker with headphones at a different volume.
Do re-measure after every meaningful gain or limiter change.

\n\n

Once the file is clean, use the same export for each feed instead of downloading it from one platform. A fresh export keeps the loudness check under your control, along with captions and safe zones.

\n\n

How UGCut handles loudness in the current development build

\n\n

In the current development build, UGCut levels the final Cut mix to -14 LUFS integrated with a -1.5 dBTP true-peak ceiling. The voice leg is levelled to -18 LUFS, leaving room for music and the Cut gain. Measurement follows ITU-R BS.1770.

\n\n

The exported file is measured again. If it lands outside -15 to -13 LUFS, or above -1.4 dBTP, the build records a warning rather than treating the export as a failure. The voice treatment chain and its loudness checks run on-device.

\n\n

Common questions about loudness for short-form video

\n\n

Is -14 LUFS required by TikTok or Instagram?

\n\n

No. -14 LUFS is the target most creators and tools work to, not a published upload requirement you should attribute to TikTok or Instagram. Use it as a starting point, then listen to the exported file at a normal phone volume and make sure the voice is easy to follow.

\n\n

Should I normalize every video to exactly the same number?

\n\n

Use the same working target for consistency, but do not flatten every creative choice to chase a decimal. A short spoken video with a quiet opening needs a listening check even when the integrated number is right. Meter the whole file, then judge voice clarity and distortion.

\n\n

Why does a loud waveform still sound quiet?

\n\n

A tall waveform may come from one plosive, music hit, or clipped transient. The words can still sit low for most of the video. Check the voice on its own, look at integrated LUFS, and listen for a limiter that is catching peaks without giving the quieter words enough useful level.

\n\n

What should I check before posting?

\n\n

Measure the whole mix, check true peak, listen for pumping and distortion, compare voice and music on a phone, export, and listen to the saved file again. If the upload is going to more than one feed, keep one clean master and make the platform copies from it.

\n\n

Make the check boring: use -14 LUFS as a working target, keep true peaks below clipping, make the voice easy to hear, then listen to the file you actually exported. UGCut is being built to keep that loudness check close to the rest of the phone edit.

","contentPlain","Use -14 LUFS integrated as a practical working target for a finished short-form mix, with true peak kept below clipping. It is not an official TikTok, Instagram, or YouTube Shorts upload requirement. Start with a clear voice, lower music under speech, check the export on the same phone volume, and resist boosting a quiet mix until it distorts.\n\nFigure: Check loudness on the finished file, not only on the timeline.\nScreenshot: /images/blog/how-loud-should-a-short-form-video-be/hero.webp\n\nAudio levels are easy to judge badly. A waveform can look tall while the words feel weak, or a mix can sound fine in your editor and turn quiet beside the next video. You need one target, a clean voice-to-music balance, and a check on the file viewers will actually hear.\n\n## How loud should a TikTok, Reel, or Short be?\n\nIf you are asking how loud a TikTok video should be, or looking for LUFS for Instagram Reels, start with -14 LUFS integrated. That is the target most creators and tools work to for a finished social mix. It gives you a repeatable starting point without promising identical playback on every phone.\n\nTikTok, Instagram, and YouTube Shorts do not publish one official upload loudness specification you can rely on here. Treat -14 LUFS as a working target for normalizing audio for social media, not a rule a platform requires. Then listen. A ten-second phone check catches problems a number cannot.\n\n## Why your video sounds quiet next to the one before it\n\nThe feed puts unlike mixes next to each other. One creator may push every word into a limiter while the next leaves more space around the voice. Your phone volume stays fixed, so the quieter average mix feels wrong even when its peaks look healthy.\n\nMusic creates the same illusion. A bright, dense song grabs attention at a lower meter reading than a soft voice over a sparse bed. Silence, long pauses, and a voice recorded far from the phone also lower the average. Find the quiet part before changing the master.\n\nWhen one video goes to several feeds, keep the audio decision in the original export. Our guide to repurposing one script for TikTok, Reels, and Shorts covers the changes around the video, not repeated re-uploads. Learn more: /blog/repurpose-one-script-for-tiktok-reels-shorts\n\n## Peak volume and perceived loudness are different\n\n### Peak is the tallest moment\n\nA peak meter answers one question: what was the loudest instant? A clap, plosive, laugh, or music hit can top the meter while the sentence sits lower. If it reaches 0 dBFS, the file can clip. Lowering the mix fixes the peak, not the quiet words.\n\n### Perceived loudness is the running experience\n\nPerceived loudness follows what you hear across time. Compression and limiting reduce the gap between quiet and loud moments, making a track feel louder without raising its highest peak. Push too far and the voice pumps, breaths stand out, and consonants lose shape.\n\nTrue peak checks for peaks between digital samples when a file is converted or played. A true-peak ceiling gives them room. That is why a mix can avoid obvious clipped samples in the editor and still crackle after encoding.\n\n## LUFS without the audio-engineering lecture\n\nLUFS measures loudness over time. The meter applies a hearing-weighted filter and averages the result, so it is closer to listening experience than a sample peak. ITU-R BS.1770 defines the measurement approach. EBU R 128 is a related framework used in broadcast and post-production tools.\n\nIntegrated LUFS considers the whole program, from first audio frame to last. A quiet intro or long pause affects the number. Short-term and momentary readings show smaller windows, useful for finding a loud section but not for describing the whole upload.\n\nFor short-form social video and many streaming workflows, -14 LUFS integrated is a sensible working target. It is not magic or a platform pass mark. A quiet opening can feel soft at -14, while a dense mix can feel tiring at the same reading. Use the number to get close, then listen.\n\n## Why chasing louder backfires\n\nThe fastest way to make a mix louder is to remove movement. A limiter catches peaks and turns the rest up, but if it works on every syllable, speech rises and falls with it. That pumping is obvious when music sits under a voice.\n\nMore level exposes distortion. Consonants flatten, music loses punch, and the video gets tiring. Some platforms may turn loud uploads down during playback normalization, so the pushed file can end up no louder than a restrained one, with less headroom and more damage.\n\nLeave room for conversion and playback. A clean mix that lands near the working target is easier to hear than a clipped mix that wins the meter for half a second.\n\n## Balance the voice and music before you master\n\nIn a talking-head video, the voice is the message. Mute the music and make the spoken line clear on a phone speaker. Bring music up until it adds energy, then lower it one step. If you have to work to catch a word, music is too loud.\n\nUse ducking when music stays present. Pull it down as speech starts, let it rise during a pause, and avoid an instant jump on every word. A slow release sounds more natural than music that vanishes and returns like a switch.\n\nCheck the loudest spoken line, quietest useful line, and music-only moment. If music has vocals, treat it as a second speaker and lower it further. Fix competing tracks before adding master gain.\n\n## A no-meter loudness check you can do on your phone\n\nYou can get a useful answer without knowing the LUFS reading. Use a reference video with a similar voice, pace, and amount of music. Our guide to making UGC videos on your phone shows a phone-first setup you can repeat before judging the audio. Learn more: /blog/how-to-make-ugc-videos-on-your-phone\n\n1. Put your reference video and your export on the same phone.\n2. Set the phone to a comfortable volume and do not touch it during the comparison.\n3. Listen to the first few seconds, one spoken sentence, and the loudest section of each video.\n4. Switch between the two without looking at the volume control.\n5. Repeat once through the phone speaker and once through the headphones you normally use.\n\nWrite down what you hear. \"The voice is buried under the music\" points to ducking. \"The whole file is soft\" points to gain or low average level. \"The loud part crackles\" points to clipping or a hard limiter. The note tells you what to change.\n\n## What to do when your desktop editor has a loudness meter\n\nA meter makes the check repeatable if you measure the right signal. Put it on the final mix bus after voice, music, effects, and limiter. Measure the entire video, not just the loudest sentence.\n\n1. Play the complete mix and read the integrated LUFS result.\n2. Use -14 LUFS integrated as your working target for the social export.\n3. Watch true peak and keep the ceiling below clipping, with room for encoding.\n4. Listen for pumping, harsh consonants, and buried words while the meter runs.\n5. Export the file, then measure that saved file again instead of trusting the timeline reading.\n\nChoosing an editor? Our guide on how to choose a video editor for UGC videos helps you score the checks that happen after creative decisions. Loudness is one of those final checks, and it should not leave you guessing which version reached the export folder. Learn more: /blog/how-to-choose-a-video-editor-for-ugc-videos\n\n## Fix a quiet upload without making it worse\n\nFirst compare the uploaded post with the saved export on the same phone, volume, and speaker. If the export is quiet, inspect the voice, ducking, and integrated reading. If the export is clear but the post is not, check the uploaded file and playback path before changing the master.\n\n- Do not raise the master until you know whether the voice or the music is quiet.\n- Do not judge from the waveform height alone.\n- Do not compare a phone speaker with headphones at a different volume.\n- Do re-measure after every meaningful gain or limiter change.\n\nOnce the file is clean, use the same export for each feed instead of downloading it from one platform. A fresh export keeps the loudness check under your control, along with captions and safe zones.\n\n## How UGCut handles loudness in the current development build\n\nIn the current development build, UGCut levels the final Cut mix to -14 LUFS integrated with a -1.5 dBTP true-peak ceiling. The voice leg is levelled to -18 LUFS, leaving room for music and the Cut gain. Measurement follows ITU-R BS.1770.\n\nThe exported file is measured again. If it lands outside -15 to -13 LUFS, or above -1.4 dBTP, the build records a warning rather than treating the export as a failure. The voice treatment chain and its loudness checks run on-device.\n\n## Common questions about loudness for short-form video\n\n### Is -14 LUFS required by TikTok or Instagram?\n\nNo. -14 LUFS is the target most creators and tools work to, not a published upload requirement you should attribute to TikTok or Instagram. Use it as a starting point, then listen to the exported file at a normal phone volume and make sure the voice is easy to follow.\n\n### Should I normalize every video to exactly the same number?\n\nUse the same working target for consistency, but do not flatten every creative choice to chase a decimal. A short spoken video with a quiet opening needs a listening check even when the integrated number is right. Meter the whole file, then judge voice clarity and distortion.\n\n### Why does a loud waveform still sound quiet?\n\nA tall waveform may come from one plosive, music hit, or clipped transient. The words can still sit low for most of the video. Check the voice on its own, look at integrated LUFS, and listen for a limiter that is catching peaks without giving the quieter words enough useful level.\n\n### What should I check before posting?\n\nMeasure the whole mix, check true peak, listen for pumping and distortion, compare voice and music on a phone, export, and listen to the saved file again. If the upload is going to more than one feed, keep one clean master and make the platform copies from it.\n\nMake the check boring: use -14 LUFS as a working target, keep true peaks below clipping, make the voice easy to hear, then listen to the file you actually exported. UGCut is being built to keep that loudness check close to the rest of the phone edit.","citations",[],"metaTitle","How Loud Should a TikTok, Reel or Short Be? | UGCut","metaDescription","Start near -14 LUFS for a short video, then check voice, music and the exported file on your phone. It is a working target, not a platform rule.","ogImageUrl","/images/blog/og/how-loud-should-a-short-form-video-be.webp","authorId",1,"categoryId","status","published","publishedAt",["D",1789779600000],"updatedAt",["D",1789779600000],"createdAt",["D",1789779600000],"readingTimeMinutes",9,"isFeatured",false,"viewCount",0,"author",{"_10":51,"_52":53,"_54":55,"_56":-5,"_57":-5,"_58":53,"_59":-5,"_60":-5,"_61":62,"_39":63,"_8":33,"_41":64},"ugcut-team","name","UGCut","bio","Notes from UGCut on planning scenes, recording takes, editing captions and preparing video for export on iPhone.","avatarUrl","jobTitle","company","twitterHandle","linkedinUrl","websiteUrl","https://ugcut.com",["D",1790643600000],["D",1790643600000],"category",{"_10":67,"_52":68,"_69":70,"_26":71,"_28":72,"_8":9,"_73":-5,"_41":74},"posting-platforms","Posting & Platforms","description","Get your video onto TikTok, Reels, and Shorts the right way: aspect ratios, captions, and repurposing one script across every platform.","Posting to TikTok, Reels & Shorts | UGCut Blog","Export and post platform-ready video: aspect ratios, captions, hooks per platform, and repurposing one script across TikTok, Reels, and Shorts.","parentId",["D",1786554000000],"faqs",[77,86,91,97],{"_8":78,"_79":9,"_41":80,"_81":82,"_83":84,"_85":48},"en:how-loud-should-a-short-form-video-be:faq:0","postId",["D",1789779600000],"question","How loud should a TikTok, Reel, or Short be?","answer","Use -14 LUFS integrated as a practical working target for the finished mix. It is not an official upload requirement from TikTok, Instagram, or YouTube Shorts. Keep the voice clear, leave headroom below clipping, and listen to the exported file on a phone before you post.","sortOrder",{"_8":87,"_79":9,"_41":88,"_81":89,"_83":90,"_85":33},"en:how-loud-should-a-short-form-video-be:faq:1",["D",1789779600000],"What does LUFS mean in video editing?","LUFS is a loudness measurement that estimates how loud a mix feels over time, rather than recording only its tallest peak. Integrated LUFS looks at the whole video, so it gives you a better view of the finished listening experience than a peak meter alone.",{"_8":92,"_79":9,"_41":93,"_81":94,"_83":95,"_85":96},"en:how-loud-should-a-short-form-video-be:faq:2",["D",1789779600000],"Why does my video sound quiet after upload?","Compare the saved export and the uploaded post on the same phone, using the same volume and speaker. If both are quiet, fix the mix. If only the post changes, check the export and playback path before raising the level and creating distortion.",2,{"_8":98,"_79":9,"_41":99,"_81":100,"_83":101,"_85":9},"en:how-loud-should-a-short-form-video-be:faq:3",["D",1789779600000],"Should music be as loud as the voice in a short video?","No. The voice carries the message, so lower music until every word stays easy to follow. Use ducking to pull the music down while someone speaks, then let it return slowly during pauses. A music track that demands attention is too loud for a talking-head video.","postTags",[104,111,117],{"_79":9,"_105":44,"_106":107},"tagId","tag",{"_10":108,"_52":109,"_41":110,"_8":44},"tiktok","TikTok",["D",1786554000000],{"_79":9,"_105":112,"_106":113},5,{"_10":114,"_52":115,"_41":116,"_8":112},"reels","Reels",["D",1786554000000],{"_79":9,"_105":118,"_106":119},7,{"_10":120,"_52":121,"_41":122,"_8":118},"shorts","Shorts",["D",1786554000000],{"_8":124,"_10":125,"_12":13,"_14":-5,"_15":-5,"_16":126,"_18":127,"_20":128,"_22":129,"_24":130,"_26":131,"_28":132,"_30":133,"_32":33,"_34":9,"_35":36,"_37":134,"_39":135,"_41":136,"_43":44,"_45":46,"_47":48,"_49":50,"_65":66,"_75":137,"_102":158},10,"repurpose-one-script-for-tiktok-reels-shorts","How to Repurpose One Script for TikTok, Reels, and Shorts","Record a script once and post it to all three feeds: aspect ratio, safe zones, caption placement, hooks that travel, and the few things that genuinely change per platform.","

Record one script once in vertical 9:16, then change only what each platform requires: the first line, the on-screen caption position, and the CTA wording. Aspect ratio, framing, and the body of your script stay the same. Export a separate file per platform so safe zones and captions stay clear.

\n\n

Most creators lose their afternoon to the wrong half of this job. They re-edit the whole video three times when the honest difference between a TikTok, a Reel, and a Short is a handful of decisions made before the export. This is the version of repurposing that takes minutes instead of an evening.

\n\n

Write one master script, not three

\n\n

A master script is the full piece: hook, body, and CTA, written to be spoken. You record it once. Everything platform-specific is a variant of two lines, not a separate document. If you keep three parallel scripts, they drift, and by the third shoot you are rewriting the body for no reason.

\n\n

Mark the two variable slots while you write. The first is the opening line, because that is where platform habits differ most. The second is the CTA, because the action you can ask for depends on where the viewer is. Our short-form video script template already separates those pieces, which is what makes this method cheap.

\n\n

Shoot vertical once and stay there

\n\n

All three feeds are portrait-first. Record vertical at 9:16 and you never re-frame. Record horizontal, or center yourself for a landscape crop, and every platform version becomes a manual reposition job with your head in the wrong third of the frame.

\n\n

Leave headroom you can afford to lose. Frame yourself so that nothing important sits in the top or bottom eighth of the picture: not your face, not the product label, not a burned-in caption. That margin is what lets one recording serve three different interface layouts without a single crop.

\n\n

Recording the master script in one sitting matters more than it sounds. A single take, read at a consistent pace with consistent framing, is what makes the three exports feel like one piece of work rather than three attempts. Reading from a prompter helps here, because you are not re-deciding the wording between platforms. Our guide on how to use a teleprompter on iPhone covers the setup that keeps a long read natural.

\n\n

What genuinely changes per platform

\n\n

The honest list is shorter than most repurposing guides suggest. Four things change, and none of them require a new edit:

\n\n

The first spoken line, because each audience arrives with a different expectation.
The CTA, because \"link in bio\" and \"follow for part two\" do not mean the same thing everywhere.
The caption position, because each app covers a different part of the frame with its own buttons and text.
The file itself, because a clean export per platform beats one upload passed around.

\n\n

Everything else is the same video. If you find yourself re-recording the body for a second platform, stop and check whether the change is real or a habit.

\n\n

What does not change, no matter the feed

\n\n

The body of your script stays put. So does your delivery, your lighting, your framing, the order of your points, the product demonstration, and the pacing you rehearsed. Attention works the same way on all three feeds: a clear promise, a visible reason to believe it, and no dead air in the middle.

\n\n

This is the part worth defending. Creators often assume a Reel needs to feel different from a TikTok, so they rewrite the middle and lose the version that already worked. Change the frame around the video, not the argument inside it.

\n\n

Safe zones: where each app covers your frame

\n\n

A safe zone is the part of the picture that no interface element sits on top of. Every app puts its own furniture over your video: a caption and username along the bottom, action buttons down one side, a progress bar or navigation strip somewhere near an edge. The exact positions move with every app update, so treat them as a moving target, not a fixed spec.

\n\n

The practical rule survives those updates. Keep the middle of the frame clear of anything you cannot afford to have covered, and check a real export on a real phone rather than trusting a template. UGCut's export presets include a safe-zone preview for TikTok, Reels, and Shorts, so you can see the overlap before you send the file anywhere.

\n\n

Put captions where all three agree

\n\n

Captions are the most common casualty of repurposing. Text that sits perfectly on TikTok can land behind a username on one platform and behind a progress bar on another. The fix is not three caption passes. It is one placement that clears the busy edges everywhere: roughly the middle band of the frame, sitting a little above center.

\n\n

Keep lines short enough to read in one glance, two lines at most, and do not stack captions against another text overlay. If you need the whole pass, from generation to line breaks, our guide on how to add captions to a video on iPhone covers it in order.

\n\n

Read the captions once before you export three files

\n\n

Any transcription error you leave in place gets multiplied by the number of platforms you post to. Read the caption track once, checking names, numbers, and any sentence where a missing word reverses the meaning. Fix it before the first export, not after the third.

\n\n

Errors cluster in predictable places: brand names, sentence endings you trailed off on, and words you said while moving a product in front of the microphone. Our explanation of why auto captions get words wrong is mostly a list of things you can fix in delivery, which means fewer corrections on the next script.

\n\n

Hooks that survive a platform switch

\n\n

A hook survives the move when it makes a specific promise about a visible result. \"Here is how I cut a talking-head video without touching a timeline\" travels, because the payoff is the same wherever the viewer is sitting. \"Part four of my series\" does not travel, because it depends on context the new audience does not have.

\n\n

Hooks that break in transit share a few traits. They reference a platform by name, they rely on a trend the other feeds never saw, they assume the viewer follows you already, or they lean on a sound that will not clear on a different app. Strip those out of the master script and keep them for the variant line.

\n\n

Vary one line, not the whole opening

\n\n

Because you tagged the opening as a variable slot, a platform variant costs one re-record of one sentence. Say the alternate first line, keep the body untouched, and swap it in. That is the entire difference between a TikTok cut and a Shorts cut in most briefs.

\n\n

The CTA deserves the same treatment. Ask for the action that exists where the viewer is watching, and say it in the words that platform's audience uses. A comment prompt, a saved video, a follow for the next part, and a link somewhere in your profile are four different asks, and only one of them usually fits a given post. Record all four as separate closing sentences while you still have the lighting set up, then attach the right one per export.

\n\n

This is also the cheapest hook test you will ever run. Three platforms with three different opening lines gives you three readings of the same script, and the body stays constant, so a difference in retention tells you something about the hook rather than about the edit.

\n\n

Trim for length, do not rewrite for it

\n\n

Each feed has its own maximum length and its own tolerance for a slower start, and those limits change often enough that it is worth checking in the app before you plan a longer piece. What does not change is the order of operations: cut whole sentences, never fragments.

\n\n

Sentence-level cutting is what makes a shorter version safe. Remove a full thought and the video still reads as written. Trim mid-sentence and you get a jump that sounds like a mistake. If your editor cuts one cut per sentence, the short version is a matter of dropping clips, not re-editing a timeline.

\n\n

Export one file per platform

\n\n

Send a separate export to each app rather than downloading your own post and reposting it. A re-uploaded file has already been compressed once, often carries the other platform's watermark, and can lose caption legibility in the second pass. A fresh export from the original take avoids all three problems.

\n\n

Name the files so you can tell them apart later, and keep the master recording. When a brand asks for a new cut in two weeks, you want the take, not the finished upload. The full path from written script to a finished file is in how to turn a script into a video.

\n\n

The ten-minute repurposing pass

\n\n

Record the master script vertically, with the middle of the frame clear.
Read the captions once and correct names, numbers, and reversed meanings.
Place the captions in the middle band, above center, two lines at most.
Re-record only the opening line for each platform variant.
Swap the CTA for the action that actually exists on that platform.
Check the safe-zone preview, then export a separate file per app.

\n\n

Run that once and repurposing stops being a second edit. It becomes the last six minutes of the first one. Before you export the three files, check the mix against our guide on how loud a short-form video should be. If you are still assembling the rest of your workflow around it, our breakdown of the UGC creator app stack shows where each of these steps lives.

","Record one script once in vertical 9:16, then change only what each platform requires: the first line, the on-screen caption position, and the CTA wording. Aspect ratio, framing, and the body of your script stay the same. Export a separate file per platform so safe zones and captions stay clear.\n\nMost creators lose their afternoon to the wrong half of this job. They re-edit the whole video three times when the honest difference between a TikTok, a Reel, and a Short is a handful of decisions made before the export. This is the version of repurposing that takes minutes instead of an evening.\n\n## Write one master script, not three\n\nA master script is the full piece: hook, body, and CTA, written to be spoken. You record it once. Everything platform-specific is a variant of two lines, not a separate document. If you keep three parallel scripts, they drift, and by the third shoot you are rewriting the body for no reason.\n\nMark the two variable slots while you write. The first is the opening line, because that is where platform habits differ most. The second is the CTA, because the action you can ask for depends on where the viewer is. Our short-form video script template already separates those pieces, which is what makes this method cheap. Learn more: /blog/short-form-video-script-template\n\n## Shoot vertical once and stay there\n\nAll three feeds are portrait-first. Record vertical at 9:16 and you never re-frame. Record horizontal, or center yourself for a landscape crop, and every platform version becomes a manual reposition job with your head in the wrong third of the frame.\n\nLeave headroom you can afford to lose. Frame yourself so that nothing important sits in the top or bottom eighth of the picture: not your face, not the product label, not a burned-in caption. That margin is what lets one recording serve three different interface layouts without a single crop.\n\nRecording the master script in one sitting matters more than it sounds. A single take, read at a consistent pace with consistent framing, is what makes the three exports feel like one piece of work rather than three attempts. Reading from a prompter helps here, because you are not re-deciding the wording between platforms. Our guide on how to use a teleprompter on iPhone covers the setup that keeps a long read natural. Learn more: /blog/how-to-use-a-teleprompter-on-iphone\n\n## What genuinely changes per platform\n\nThe honest list is shorter than most repurposing guides suggest. Four things change, and none of them require a new edit:\n\n- The first spoken line, because each audience arrives with a different expectation.\n- The CTA, because \"link in bio\" and \"follow for part two\" do not mean the same thing everywhere.\n- The caption position, because each app covers a different part of the frame with its own buttons and text.\n- The file itself, because a clean export per platform beats one upload passed around.\n\nEverything else is the same video. If you find yourself re-recording the body for a second platform, stop and check whether the change is real or a habit.\n\n## What does not change, no matter the feed\n\nThe body of your script stays put. So does your delivery, your lighting, your framing, the order of your points, the product demonstration, and the pacing you rehearsed. Attention works the same way on all three feeds: a clear promise, a visible reason to believe it, and no dead air in the middle.\n\nThis is the part worth defending. Creators often assume a Reel needs to feel different from a TikTok, so they rewrite the middle and lose the version that already worked. Change the frame around the video, not the argument inside it.\n\n## Safe zones: where each app covers your frame\n\nA safe zone is the part of the picture that no interface element sits on top of. Every app puts its own furniture over your video: a caption and username along the bottom, action buttons down one side, a progress bar or navigation strip somewhere near an edge. The exact positions move with every app update, so treat them as a moving target, not a fixed spec.\n\nThe practical rule survives those updates. Keep the middle of the frame clear of anything you cannot afford to have covered, and check a real export on a real phone rather than trusting a template. UGCut's export presets include a safe-zone preview for TikTok, Reels, and Shorts, so you can see the overlap before you send the file anywhere. Learn more: /app/features/platform-export\n\n## Put captions where all three agree\n\nCaptions are the most common casualty of repurposing. Text that sits perfectly on TikTok can land behind a username on one platform and behind a progress bar on another. The fix is not three caption passes. It is one placement that clears the busy edges everywhere: roughly the middle band of the frame, sitting a little above center.\n\nKeep lines short enough to read in one glance, two lines at most, and do not stack captions against another text overlay. If you need the whole pass, from generation to line breaks, our guide on how to add captions to a video on iPhone covers it in order. Learn more: /blog/how-to-add-captions-to-a-video-on-iphone\n\n## Read the captions once before you export three files\n\nAny transcription error you leave in place gets multiplied by the number of platforms you post to. Read the caption track once, checking names, numbers, and any sentence where a missing word reverses the meaning. Fix it before the first export, not after the third.\n\nErrors cluster in predictable places: brand names, sentence endings you trailed off on, and words you said while moving a product in front of the microphone. Our explanation of why auto captions get words wrong is mostly a list of things you can fix in delivery, which means fewer corrections on the next script. Learn more: /blog/why-auto-captions-get-words-wrong\n\n## Hooks that survive a platform switch\n\nA hook survives the move when it makes a specific promise about a visible result. \"Here is how I cut a talking-head video without touching a timeline\" travels, because the payoff is the same wherever the viewer is sitting. \"Part four of my series\" does not travel, because it depends on context the new audience does not have.\n\nHooks that break in transit share a few traits. They reference a platform by name, they rely on a trend the other feeds never saw, they assume the viewer follows you already, or they lean on a sound that will not clear on a different app. Strip those out of the master script and keep them for the variant line.\n\n## Vary one line, not the whole opening\n\nBecause you tagged the opening as a variable slot, a platform variant costs one re-record of one sentence. Say the alternate first line, keep the body untouched, and swap it in. That is the entire difference between a TikTok cut and a Shorts cut in most briefs.\n\nThe CTA deserves the same treatment. Ask for the action that exists where the viewer is watching, and say it in the words that platform's audience uses. A comment prompt, a saved video, a follow for the next part, and a link somewhere in your profile are four different asks, and only one of them usually fits a given post. Record all four as separate closing sentences while you still have the lighting set up, then attach the right one per export.\n\nThis is also the cheapest hook test you will ever run. Three platforms with three different opening lines gives you three readings of the same script, and the body stays constant, so a difference in retention tells you something about the hook rather than about the edit.\n\n## Trim for length, do not rewrite for it\n\nEach feed has its own maximum length and its own tolerance for a slower start, and those limits change often enough that it is worth checking in the app before you plan a longer piece. What does not change is the order of operations: cut whole sentences, never fragments.\n\nSentence-level cutting is what makes a shorter version safe. Remove a full thought and the video still reads as written. Trim mid-sentence and you get a jump that sounds like a mistake. If your editor cuts one cut per sentence, the short version is a matter of dropping clips, not re-editing a timeline. Learn more: /blog/auto-cut-video-by-sentence\n\n## Export one file per platform\n\nSend a separate export to each app rather than downloading your own post and reposting it. A re-uploaded file has already been compressed once, often carries the other platform's watermark, and can lose caption legibility in the second pass. A fresh export from the original take avoids all three problems.\n\nName the files so you can tell them apart later, and keep the master recording. When a brand asks for a new cut in two weeks, you want the take, not the finished upload. The full path from written script to a finished file is in how to turn a script into a video. Learn more: /blog/how-to-turn-a-script-into-a-video\n\n## The ten-minute repurposing pass\n\n1. Record the master script vertically, with the middle of the frame clear.\n2. Read the captions once and correct names, numbers, and reversed meanings.\n3. Place the captions in the middle band, above center, two lines at most.\n4. Re-record only the opening line for each platform variant.\n5. Swap the CTA for the action that actually exists on that platform.\n6. Check the safe-zone preview, then export a separate file per app.\n\nRun that once and repurposing stops being a second edit. It becomes the last six minutes of the first one. Before you export the three files, check the mix against our guide on how loud a short-form video should be. If you are still assembling the rest of your workflow around it, our breakdown of the UGC creator app stack shows where each of these steps lives. Learn more: /blog/how-loud-should-a-short-form-video-be /blog/ugc-creator-app-stack",[],"Repurpose One Script for TikTok, Reels & Shorts | UGCut","Record one script and post it to TikTok, Reels, and Shorts. Aspect ratio, safe zones, caption placement, hooks that travel, and what changes per platform.","/images/blog/og/repurpose-one-script-for-tiktok-reels-shorts.webp",["D",1787056200000],["D",1789779600000],["D",1787056200000],[138,143,148,153],{"_8":139,"_79":124,"_41":140,"_81":141,"_83":142,"_85":48},"en:repurpose-one-script-for-tiktok-reels-shorts:faq:0",["D",1789779600000],"Can I post the same video file to TikTok, Reels, and Shorts?","You can, but export a fresh file for each app instead of downloading your own post and reuploading it. A re-uploaded file has already been compressed once, may carry another platform's watermark, and often loses caption legibility in the second pass.",{"_8":144,"_79":124,"_41":145,"_81":146,"_83":147,"_85":33},"en:repurpose-one-script-for-tiktok-reels-shorts:faq:1",["D",1789779600000],"What aspect ratio should I record for all three platforms?","Record vertical at 9:16. All three feeds are portrait-first, so a single vertical take serves every platform without re-framing. Keep the top and bottom eighth of the picture free of anything important, because that is where each app places its own interface.",{"_8":149,"_79":124,"_41":150,"_81":151,"_83":152,"_85":96},"en:repurpose-one-script-for-tiktok-reels-shorts:faq:2",["D",1789779600000],"Where should captions sit so they are not covered?","Put them in the middle band of the frame, a little above center, at two lines maximum. The bottom carries usernames and post text, one side carries action buttons, and the exact positions shift with app updates, so check a real export on a phone.",{"_8":154,"_79":124,"_41":155,"_81":156,"_83":157,"_85":9},"en:repurpose-one-script-for-tiktok-reels-shorts:faq:3",["D",1789779600000],"Do I need a different script for each platform?","No. Write one master script and treat the opening line and the CTA as variable slots. Re-record just those two sentences per platform and keep the body identical. Rewriting the middle is what turns a ten-minute repurposing pass into a second full edit.",[159,160,161,162],{"_79":124,"_105":44,"_106":107},{"_79":124,"_105":112,"_106":113},{"_79":124,"_105":118,"_106":119},{"_79":124,"_105":163,"_106":164},6,{"_10":165,"_52":166,"_41":167,"_8":163},"scripts","Scripts",["D",1786554000000],"currentPage","totalPages","siteName","footerCategories",[173,176,179,180,183],{"_10":174,"_52":175},"creator-business","Creator Business",{"_10":177,"_52":178},"editing-captions","Editing & Captions",{"_10":67,"_52":68},{"_10":181,"_52":182},"recording","Recording & Teleprompter",{"_10":184,"_52":185},"scriptwriting","Scriptwriting","actionData","errors"]