What Suffix Lines helps you do

Append the same suffix to every line, such as a comma or a file extension. It pairs with prefixing for building lists, SQL snippets or formatted data. The suffix is literal text, so it does not know whether the final line should omit a delimiter.

The operation runs locally in your browser and nothing is uploaded to Haivix.

How it works

Line tools split the pasted text into lines, apply one operation to the list, and rejoin it with a newline. A blank line is still a line, so it participates in sorting, numbering and shuffling unless you remove it first. The transformation runs in the browser and keeps the existing line order except where the tool's purpose is to change it. Nothing is uploaded, and the output replaces the preview rather than the source. If the input ends with a newline, the final empty line can affect a count or a shuffle; trim the input first when that matters.

How to use Suffix Lines

Paste the lines.
Enter the suffix to append to each line.
Apply and check the first and last lines.
Copy the suffixed result.

When to use it

Add a trailing comma to every line for a code list.
Append an extension to a list of filenames.
Add a semicolon to each line before combining them.
Append a unit to a column of numbers.
Add a closing tag to each line of a fragment.
Prepare values for a concatenation step.

When not to use it

Do not use it when the final line must omit the separator.
Do not use it on code where the suffix changes syntax.
Do not expect blank lines to be skipped automatically.

Example

Appending a comma to three value lines produces value one comma, value two comma and value three comma. The last line also gets a comma, so remove it manually if the destination rejects a trailing delimiter. A blank line would become just a comma.

What you can do with Suffix Lines

Add a suffix of up to 200 characters to every line.
Include blank lines as well as text lines.
Use a comma, semicolon, extension or other literal text.
Keep the original line content before the suffix.
Copy the suffixed block.
Run the operation locally with no upload.

Example: check the line structure first

Paste a small sample and note how many lines it has, including blank lines and a possible trailing newline. The count explains most surprises after sorting, numbering or filtering.

Apply the operation and compare the first and last lines with the source. If the structure is right, run the full text; if not, remove the blank lines or trim the input first.

Copy or download the result and keep the original until the destination accepts it. Line tools are one-way, so the source is the only undo.

For a list pasted from a spreadsheet, check for hidden carriage returns or wrapping quotes before transforming it. A stray quote can sort differently or survive a filter that looks correct at a glance.

When the result feeds another tool, run a second pass only after confirming the first. Chaining a sort and a deduplication is safe, but chaining two numbering steps produces duplicated prefixes.

If the output is going into a version-controlled file, check the diff before committing. A blank-line or line-ending change can look like a content change in review even when the words are unchanged.

What to know before you start

The suffix is added even to the last line, unlike a real CSV that omits the final delimiter.
Blank lines also receive the suffix unless you remove them first.
There is no conditional or per-line suffixing.
The suffix is capped at 200 characters.

Common mistakes

Leaving a trailing delimiter on the final entry.
Appending a suffix to blank lines and creating stray punctuation.
Expecting the tool to escape the suffix for a specific language.
Applying it to code and changing the syntax.

Troubleshooting

If the last line has an unwanted delimiter, delete it after the transformation.

If blank lines became punctuation-only, remove empty lines first.

If the suffix is truncated, it exceeded the 200-character limit.

If the suffix appears twice, the source already had it.

Suffix Lines