Add text in CapCut by generating an exact-length string with Text Padder, pasting the result into CapCut's built-in text tool, then dragging the resulting clip onto your timeline. Text Padder extends any source text to a precise Unicode code-point length — anywhere from zero up to one million characters — by repeating a pattern on the left, the right, or split across both sides. You choose the original words, the target length, the pattern (such as a row of dots, dashes, or any custom string), and which side receives the fill. Once padded, the result downloads as a UTF-8 TXT file you can paste straight into a CapCut text box as a title card, caption, lower third, watermark, or chapter marker. Every step runs locally in your browser, so the words you pad never leave the tab you opened them in. This makes the workflow well suited for fixed-width overlays, repeated header bars, and any label that must keep a predictable visual width across scenes.
What "Add Text" Means in CapCut
CapCut ships with a text tool inside its editor on every platform: phone, desktop, and the web version. When you tap "Text" in the toolbar, you can drop a title, subtitle, or body block directly over a video clip. That is the standard way to add text in CapCut, and it is the right starting point for almost every project. The built-in text tool handles styling, animation presets, font selection, color, opacity, and the duration of the text on the timeline.
The catch shows up when you need the text inside that box to keep a precise, predictable length. A raw title like "Sale" is four characters, while "Summer Sale 2026" is sixteen. If you want every overlay card in your video to match the same visual width — say, a fixed 20-character banner — typing each one by hand is slow and error-prone. That is the gap Text Padder fills. You do not replace CapCut's text tool; you feed it pre-shaped strings so every overlay is the same length before styling begins.
When Exact-Length Text Helps a CapCut Project
Several recurring CapCut tasks look cleaner with fixed-length text:
- Chapter or section markers where every label must occupy the same horizontal line on screen.
- Lower thirds that name a speaker, where the colon and the role description should line up across cuts.
- Watermarks and logos repeated in the same corner, frame after frame, without drifting in size.
- Quiz cards, countdown timers, or step indicators that need consistent reach to the right edge.
- Headers that frame a centered title with a balanced run of dots, asterisks, or em dashes.
In each case, padding gives the source string a deterministic width so the rest of the layout stays predictable. Designers who mock up a frame in a fixed-width font get the same shape once they paste the padded text into CapCut's text box.
Generate the Padded Text in Three Steps
- Open Text Padder and paste your source string into the input field. Type the target length in Unicode code points — a whole number from 0 through 1,000,000. For a 20-character banner, enter 20.
- Type a nonempty padding pattern. A single character works ("·", "-", "*"), but longer patterns repeat just as cleanly ("=-", "..."). Choose a side: left, right, or both. Click Pad.
- Review the preview and the reported code-point length. If everything matches, click Download to save the result as a UTF-8 TXT file, then paste the text into a CapCut text box. Drop the resulting clip on your timeline and style it as usual.
The original source remains visible in the input so you can adjust the pattern or side and re-run. Changing any field clears the previous result, so an old preview cannot be mistaken for the new settings. If the source already meets or exceeds the target, Text Padder returns it unchanged — it never truncates text to force a shorter result.
Pick the Pattern and Side That Fit Your Clip
The choice of pattern and side shapes the final overlay. A single character pattern produces clean bars ("----" or "····"). A two-character pattern produces textured bars ("=-=-"). Patterns can be any nonempty text, including emoji, punctuation, spaces, or letter runs.
| Overlay style | Best side | Why it fits |
|---|---|---|
| Centered title with a balanced border | Both sides | Symmetric fill keeps the title visually centered in the frame. |
| Right-aligned timestamp or clock | Left | Adds characters before the time so the visible string sits at the right edge. |
| Left-aligned chapter name | Right | Keeps the chapter name flush left while filling the trailing space. |
| Banner running across the frame | Both sides | Creates a balanced border of dots, dashes, or stars around the source. |
| Watermark fixed in one corner | Right or left | One-sided fill keeps the source pinned in a consistent position. |
A worked example shows the math. Take the source "Hi" — 2 code points — with a target of 8 and the pattern "•" on both sides. The missing length is 8 − 2, which equals 6 code points. Splitting 6 evenly across both sides gives 3 on the left and 3 on the right. The final string is "•••Hi•••", which is 8 code points long. Confirm the count with the on-screen length, then paste the result into a CapCut text box.
When the missing length is odd, the both-sides rule still applies: the right side receives the extra code point. Padding "Hi" to length 7 on both sides gives 2 on the left and 3 on the right, producing "••Hi•••". The rule is fixed and deterministic, so your previews match across runs.
How Unicode Code Points Shape the Count
Text Padder measures length by iterating the source with JavaScript's string iterator, which counts Unicode code points rather than UTF-16 code units. Most single emoji count as one code point, so a string like "Hi 😊" is 4 code points, not 5. Combining marks count separately from their base letter, and joined emoji sequences can contain several code points even when they look like one glyph on screen. The tool reports this code-point model explicitly so the number is not confused with visual glyphs, bytes, words, or grapheme clusters.
This matters when you paste the padded result into CapCut. The reported code-point length is a text length, not a visual width or a byte count. A wide CJK character, a tab, a proportional-font letter, or an emoji glyph can occupy a different number of pixels than the count implies. Use the reported length to verify your padding ran correctly, but always check the CapCut preview before locking the frame. If a specification requires a fixed byte length — a database column, a binary protocol, or a UTF-8 encoded file — reach for a format-aware byte tool rather than Text Padder, because the same code-point count can translate to different byte counts.
Limits and Quick Fixes
A few boundaries are worth knowing before you run a large job:
- The target must be a non-negative whole number. Decimal, negative, missing, or nonnumeric entries are rejected, so set a whole number up to 1,000,000.
- Padding text must be nonempty when characters need to be added. Spaces, line breaks, punctuation, emoji, and multi-character patterns all qualify because they are ordinary text.
- Inputs longer than one million code points are not expanded, and the target itself cannot exceed the documented ceiling. The ceiling bounds memory use, repeated concatenation, preview rendering, and download creation.
- If the source already meets or exceeds the target, Text Padder returns the source unchanged. It never truncates, so set a larger target when padding is required.
- A zero target is valid but leaves nonempty source text unchanged under the same no-truncation rule.
Invisible padding — strings made of zero-width characters or repeated spaces — can be hard to inspect by eye. Trust the reported length and the downloaded TXT file rather than the on-screen preview alone. The download button creates a temporary Blob URL only when clicked, starts the browser download, and revokes the URL immediately, so there is nothing to clean up afterwards. The same accepted source, target, pattern, and side always produce the same string, which makes the output reproducible across runs.
The padding, previewing, and TXT download creation follow the MDN documentation on the Blob interface used for downloads and the MDN string iterator documentation that defines code-point iteration, both linked inside the tool page for readers who want to inspect the underlying spec.
If you're weighing options, How to Add Text in DaVinci Resolve With Exact-Length Labels covers this in detail.
If you're weighing options, How to Add Text in iMovie With Exact-Length Labels covers this in detail.