Plain text and code
Merge TXT, Markdown, logs, subtitles, SQL and other UTF-8 text. Choose separators, line endings and optional filename headings.
Combine compatible text and structured data files into one clean download. Arrange the order, control how content joins, and preview your result—entirely in your browser.
Only compatible files can be combined in each mode.
Original files are never modified. The order shown here is the order used for merging.
Choose how one text file meets the next.
Union adds missing columns and fills blank values. Column names must be unique within each file.
JSON documents load into memory for structural merging. Limit: 24 MiB per file and 64 MiB total.
Every nonempty line is validated as JSON. Output uses UTF-8 and LF line endings. Invalid records stop the export.
Different file formats need different rules. Select the merge mode that matches the structure of your source files.
Merge TXT, Markdown, logs, subtitles, SQL and other UTF-8 text. Choose separators, line endings and optional filename headings.
Combine rows without repeating headers. Match fields by name or position, track source filenames, optionally remove duplicates, and export as CSV or TSV.
Concatenate arrays, combine objects, deep-merge nested properties or collect individual documents with names.
Combine newline-delimited JSON records, validate each line and stream the result without loading the full dataset.
No. File reading, validation, merging and export happen in your browser. This standalone tool does not send your files to a server.
Yes. Choose CSV / TSV and “Union by column name.” The merged file contains the combined set of column headers, with missing values left blank. Duplicate or ambiguous headers inside a source file are rejected.
Yes. Use “Collect documents with filenames” to wrap each original document in an output array. For array concatenation or object merging, all files must have the corresponding top-level structure.
No. Those are binary or container formats and cannot safely be concatenated as text. Use a dedicated PDF, document, video or archive tool instead. HTML, XML, SRT and VTT may be concatenated as plain text, but the result is not guaranteed to be a valid combined document or subtitle track.
Text, table and JSONL modes read input in chunks. In supported browsers, direct-to-disk saving avoids building one giant file in memory. Other browsers use a download fallback limited to 150 MiB of output. Structured JSON merging has stricter memory limits. Optional CSV duplicate removal also has a bounded memory index.
Combine compatible local text, CSV/TSV, JSON or JSONL files in a deliberate order, review merge rules, and save the merged result.
Merge two JSONL logs in chronological order, validate each input, then download the combined file and spot-check the boundary records.
This is type-aware merging, not PDF, Office, archive, media or arbitrary binary concatenation. Structured input must validate. CSV header normalization, deduplication and optional formula protection can change text fidelity. JSON allows 24 MiB per file and 64 MiB combined. Native streaming and the bounded Blob fallback have different limits. Files are processed locally.
No. Supported inputs are text, CSV/TSV, JSON and JSONL; it does not combine document formats or arbitrary binary files.
Not always. The optional protection can alter cell text; review output if exact text fidelity matters.