Merging text files into Excel is a two-stage process: combine the source files locally into a single UTF-8 text file, then import that combined file through Excel's Text Import Wizard or its modern "Get Data" menu. The first stage controls file order, separator characters, and encoding; the second stage controls how Excel splits the combined result into rows and columns. Skipping either stage, or expecting a single tool to do both at once, is how people end up with scrambled rows, broken delimiters, or empty worksheets. Text File Merger handles stage one in your browser by joining 2–20 TXT, CSV, MD, or LOG files (up to 10 MiB total) in the exact order you select them, with a separator you choose between one newline, one blank line, or nothing. The tool never uploads files, never changes your originals, and produces a single merged-text.txt that you can then import into Excel with explicit column delimiters.
Merging and Importing Are Two Separate Jobs
Most search results treat "merge text files into Excel" as if there is a single magic button. There isn't. Merging and importing are two separate operations, and conflating them is the root of almost every "my data looked right but Excel put everything in one column" complaint.
Merging means taking the raw text content of two or more files and producing one combined file in a chosen order, with a chosen separator between them. The output is still text. Importing means opening that combined text inside Excel with delimiters, data types, and column rules that tell Excel where one cell ends and the next begins. Text File Merger performs the merge; Excel performs the import. Once you see them as two stages, the rest of the workflow becomes much easier to debug.
This split is also why the merged file is downloaded as a plain merged-text.txt rather than a .xlsx workbook. The tool does not pretend to know how Excel will interpret your columns, because that depends on delimiter, encoding, and header choices you make during the second stage.
File Types, Sizes, and Other Limits the Tool Enforces
Text File Merger is deliberately narrow about what it accepts. The accepted filename extensions are TXT, CSV, MD, and LOG, and the combined input is capped at 10 MiB before any file is read. If the total exceeds 10 MiB by even one byte, the merge is rejected before any content is decoded. You need at least two files; a one-file merge is not a merge. The maximum is twenty files.
| Accepted extension | How the tool treats it | Implication for Excel |
|---|---|---|
| TXT | Decoded as plain text, characters joined verbatim | Safe to import with any delimiter Excel detects |
| CSV | Decoded as plain text; CSV quoting, headers, and quoted multiline records remain ordinary characters | Safe only when every CSV uses the same schema, delimiter, encoding, and header row |
| MD | Decoded as plain text; Markdown syntax is preserved, not stripped | Useful for stitching chapters; not a substitute for a Markdown-aware parser |
| LOG | Decoded as plain text; log records and timestamps remain characters | Useful for appending excerpts; parsing still happens in Excel or another tool |
The tool treats every accepted file as text. Renaming a binary file to .txt does not turn it into a format-aware parser, and a binary file decoded as text may show replacement characters. Inspect the preview before you trust the result.
How to Merge Text Files Step by Step
- Open Text File Merger in your current browser tab.
- In the file picker, select two to twenty files with TXT, CSV, MD, or LOG extensions, in the exact order you want them to appear in the combined result.
- Choose one separator: One newline (a single LF between files), One blank line (two LF characters), or No separator (the previous file's last character sits directly against the next file's first character).
- Click the merge action. The tool reads each file locally, joins the decoded strings in picker order with the chosen separator, and renders the exact combined result in the preview area.
- Inspect the preview carefully. If a file appears in the wrong position, reselect the files in a different order; the tool never sorts by name, date, or size.
- Click download to save the result as merged-text.txt. The download uses a temporary UTF-8 Blob URL that is revoked immediately, so no upload happens and no Blob URLs accumulate.
Browser file pickers usually preserve selection order, but confirm that in the preview when order matters. Selecting new files or a new separator clears the previous result so a stale output cannot be confused with the current inputs.
Choosing the Right Separator for Excel-Compatible Output
Each separator option inserts a specific, fixed character sequence between files. None of them trims existing line breaks inside each file, and none of them deduplicates boundaries. Existing leading and trailing line breaks inside each decoded file remain exactly as the browser read them, so a file that already ends in LF plus the blank-line option will produce three consecutive LF characters before the next file begins.
| Separator option | Characters inserted between files | Effect during Excel import |
|---|---|---|
| One newline | Exactly one LF | Adjacent files share a single line break, useful for continuous lists where each file is a continuation |
| One blank line | Exactly two LF characters | Adjacent files are visually separated by a blank line; the most common choice for stacking chapters, notes, or log excerpts |
| No separator | Nothing inserted | Adjacent files are glued character-for-character; pick this only when each file already ends with the exact character the next file should immediately follow |
For Excel, the most reliable starting point is one blank line, because Excel's import wizards treat blank lines as record separators more predictably than ambiguous single-newline joins. If your files already end with their own consistent line break and you want a tight concatenation, choose one newline. No separator is a power-user option and almost always produces a result that requires manual cleanup inside Excel.
Importing the Merged File Into Excel
Once you have merged-text.txt, the second stage begins: importing the file into Excel. Excel handles this through the Text Import Wizard in older releases or the "Get Data" workflow in Excel 2016 and later.
- In Excel, open a blank workbook or pick the worksheet where you want the combined data to land.
- On the Data tab, choose Get Data → From File → From Text/CSV (Excel 2016+) or From Text in older versions.
- Select the downloaded merged-text.txt file. Excel opens a preview pane that detects file origin, delimiter, and data type detection.
- Confirm the delimiter matches what your source files actually used (comma, tab, semicolon, or another character). The delimiter detection is independent of the separator you chose during the merge stage; the merge stage controls inter-file joins, while this dialog controls intra-file column splits.
- If your first file contains headers, mark My data has headers and Excel promotes that row. Be aware that if every merged file contains its own header, every header row except the first will appear as a data row, because Text File Merger does not strip repeated headers.
- Click Load to place the combined content in your worksheet.
If the preview looks wrong, click Transform Data in the preview pane to open Power Query and adjust delimiters, data types, and header rows with full undo. For a quick sanity check before importing, open the file in any text editor and confirm the line count matches what you saw in the merge preview.
CSV Compatibility, Logs, and Other Things to Check First
Text File Merger is explicit about what it does not do. It does not validate that CSV files share a schema, it does not strip repeated headers, it does not understand Markdown structure, and it does not parse log records. Concatenation works because the tool only joins strings; structure is preserved because the tool changes nothing inside each file.
That makes three pre-merge checks essential. First, if you are stacking CSV files, confirm that every file uses the same delimiter, the same quoting style, the same encoding (UTF-8 is safest), and the same number of columns per row. Mismatched CSV schemas will produce an Excel sheet with rows of inconsistent width, and the tool will not warn you. Second, if your source files are LOG records, decide whether timestamps need to be sorted; the merger preserves picker order, not chronological order. Third, if your source files are Markdown chapters, the # headings will appear as ordinary lines in Excel because no Markdown parsing happens during the merge.
For sensitive data or files that approach the 10 MiB cap, prefer a local command-line utility with explicit encoding and streaming behavior, since the browser version is intended for bounded convenience rather than archival preservation. Keep the originals until you have opened merged-text.txt in Excel and confirmed the import looks correct; the same decoded strings, in the same order, with the same separator will always reproduce the same result, so an unexpected output is almost always an input or import-wizard issue rather than a tool bug.
If you want a faster, three-step shortcut that skips most of the configuration above, the local merge workflow for Excel covers the same ground in a more compressed format. The detailed steps in this article are useful when you have more than a handful of files, mixed extensions, or an import that needs careful delimiter and header handling.
If you're weighing options, Compare Two Lists for Matches in Excel Locally covers this in detail.