Text Padding Tool

Pad each text line to a minimum Unicode code-point length on the left or right without truncating longer lines.

Minimum width counts code points, not display columns. Padding is exactly one code point; existing longer lines are not truncated.

Input stays in this browser. Source limit: 100,000 UTF-16 code units. Output limit: two million characters.

Text Padding Tool: an explicit text transformation

Enter text, set Minimum code points per line, choose Left or Right, and enter one Padding character. The example chooses width five, Right, and a period. Cat gains two periods; the emoji is one code point and gains four; longer already exceeds the minimum and is unchanged.

Inspect the example result

Choose Load example (replaces input and settings) and then Process text. Expected result: cat.., 😀.... and longer on separate lines. The example replaces existing input and options; keep your original separately if needed.

Exact rules and boundaries

Each logical line is padded independently. Existing spaces and tabs count as code points. Empty lines inside the source are padded, but a final newline is retained without adding a new padded phantom line. Output separators are LF. The padding value must contain exactly one Unicode code point and cannot be CR or LF.

Code-point length does not predict visual alignment. Combining marks, emoji sequences, wide glyphs and tabs can occupy different screen widths. A supplementary-plane symbol is one permitted padding code point; a multi-code-point grapheme is rejected. No input is truncated and there is no numeric sign-aware formatting.

Limits and export

Minimum padding width accepts 1–1,000 code points. Large requested output is rejected before padding strings are allocated. Source input supports 100,000 UTF-16 code units. Line-based operations accept 10,000 logical lines, excluding an empty final segment after a trailing terminator. Unpaired UTF-16 surrogates are rejected to avoid replacement during UTF-8 export. Browser textareas can normalize line endings before processing.

Changing source or any option clears the old result and download. Copy and download contain the complete padded TXT. Projected output is capped at two million UTF-16 code units before padding is allocated. Processing does not modify a local source file or send entered text to a conversion service.

Use Unicode Code Point Inspector to investigate unexpected lengths. Use Text Wrapping Tool to insert hard code-point-based line breaks rather than extending short lines.