Text Merger

📖 Tool Introduction

Text Merger is a lightweight tool that stitches many plain-text files into a single file in order. When you write chapters as separate drafts, rotate logs into daily files, or split a frontend stylesheet into fragments, everything eventually has to go back into one complete document. Drop the files in one after another and they line up as a numbered queue, each row showing the name and size with a remove button on the right, so a mistaken add can be deleted and redone on the spot. Below the queue you choose how the pieces are joined: directly with no separator, with a blank line, with a single newline, or with any custom text you type in, such as ===== or //----. Tick the annotate option and each piece starts with a ===== filename ===== heading, so the source of every passage stays obvious. Click Merge now and the tool reads the queued files one by one as UTF-8, joins them by your rule, and shows the complete result in the output area together with live counts of characters, lines and contributing files. The result can be copied in one click or saved as merged-text.txt. The whole loop runs in your browser, so long chapters, logs and code fragments are never uploaded anywhere.

✨ Key Features

• Ordered queue: numbered by add order, and order is merge order
• Flexible separators: none, blank line, single newline or custom text
• Filename headers: each piece gets a ===== filename ===== heading
• Live stats: characters, lines and file count shown after merging
• Quick output: copy the result or download merged-text.txt in two steps
• Local loop: files are read as UTF-8 one by one, zero uploads

📝 How to Use

1. Drop the text files to merge into the dashed area, one after another, or multi-select
2. Confirm the order in the queue; remove a wrong file with its ✕ button
3. Pick a separator, type custom content when needed and tick filename annotation
4. Click Merge now and inspect the joined result in the output area
5. Copy the result or download merged-text.txt for your records

⚠️ Notes

• Order is result: merge order equals queue order; reorder by removing and re-adding
• Read as text: files are read as UTF-8 text, so binaries are not suitable
• Trailing newline: pieces may stick together without a newline; prefer blank-line separation
• Consistent encoding: keep every file in UTF-8 to avoid garbled characters
• Privacy: all reading and joining happens locally in the browser

🧰 Common use cases

People merge text files far more often than they expect: chapters of a manuscript split across drafts, server logs rotated by day, interview transcripts cut by speaker, and code fragments assembled from snippets. This tool queues your pieces in the order you add them and joins them by a rule you control. Blank-line separation suits prose so paragraphs stay legible, while no separator suits code where extra newlines would break the snippet; a custom separator lets you insert exactly the marker your downstream system expects. Filename headings make the joined file self-documenting, so anyone reading the merged result later can tell which passage came from which source. Files are read one by one as UTF-8, so the queue never sits in memory all at once. Copy the result or save it as merged-text.txt, and remember the merge order is literally the queue order, which is why removing and re-adding is the way to reorder.