FileGizmo Text tools
Wrap text at a column width
Reflow paragraphs to a fixed column width for commit messages, plain-text email and fixed-width output, with long words and URLs kept intact by default.
Complete
Your result is ready
Simple by design
Wrap text in three steps
Fixed-width text has not gone away. Commit message bodies are conventionally wrapped at 72 columns, plain-text email still expects a hard wrap, and plenty of code review tools, changelogs, README files and terminal output are read at a fixed width whether or not anyone wrote them that way.
The default here is 72 columns, which is the convention for a commit body and leaves room for the indentation that a mail client or a git log adds when quoting it.
The choice that changes the result most is whether to reflow. Reflowing joins each paragraph back into one run of text and then breaks it at the chosen width, which is what prose needs: text that was previously wrapped at a different width comes out wrapped at the new one, with no trace of where the old breaks were. Blank lines separate paragraphs and are preserved, so the structure survives while the line breaks inside it are rebuilt.
Wrapping each line where it already sits does the opposite. It leaves the existing line structure alone and only breaks lines that are too long. This is the mode for anything that is already laid out deliberately, where joining lines would destroy the layout: a list, a table of contents, a block of code, or text whose line breaks are meaningful.
Long words are the only genuinely difficult case. A URL, a long identifier or a file path can easily exceed the whole column width, and there are two ways to handle it. Breaking it produces a tidy right margin and a link that no longer works when clicked or copied. Keeping it whole produces one line that overshoots the column. FileGizmo keeps it whole by default, on the grounds that an overshooting line is visible to whoever is looking at the text while a silently broken URL is not. Breaking is available for the cases where the column really is a hard limit.
The wrapping itself is greedy: each line takes as many words as fit and then breaks. More sophisticated algorithms balance the ragged edge across the whole paragraph and produce a visibly nicer margin, but no editor does that, so the output would stop matching what the same text looks like anywhere else. Agreeing with the tools around it is worth more than the prettier margin.
The result reports the number of lines produced and the width they were wrapped to. Nothing is uploaded.
- 1
Paste a paragraph a commit message or an email
- 2
Set the column width and choose whether to reflow paragraphs
- 3
Press Wrap the text and copy or download the result
Good to know
Frequently asked questions
What happens to a word longer than the width?
It is kept whole by default and allowed to overshoot the column. Breaking it would mangle a URL or a long identifier, and an overshooting line is visible while a broken link is not. Breaking can be turned on.
What is the difference between reflowing and wrapping each line?
Reflowing joins a paragraph back together before breaking it at the new width, which is what you want for prose. Wrapping each line where it sits preserves the existing line structure, which is what you want for anything already laid out.
Why does it not balance the ragged edge?
Because editors do not. The wrapping is greedy, which is the same result your editor gives, and matching that is more useful than a prettier right margin nobody else will reproduce.
What widths are allowed?
Anything from 8 to 400 columns. The default is 72, which is the conventional width for a commit message body and plain-text email.
Learn more