Converting CSV files and pasted tables into printable PDFs
Raw spreadsheet exports from banks, accounting software, and database queries are awkward to share for signatures or printouts because plain text wraps unpredictably across pages. Converting delimited records locally in your browser produces a crisp, paginated PDF table while keeping 0 bytes of financial or customer data off external servers.
Inspecting the 50-row preview and 20 MB browser file cap
Drop any .csv, .tsv, or .txt export up to 20 MB onto the drop zone, or choose the paste option to edit raw rows in a monospace text box. Uploaded files show a scrollable 50-row HTML preview alongside exact row, column, and detected delimiter counts while exporting every row to PDF.
As noted in the Library of Congress CSV Format Description, plain delimited text preserves tabular records without proprietary workbook overhead. If your source file is a styled .xlsx spreadsheet with merged cells or formulas, you can turn formatted Excel workbooks into PDF tables directly instead.
Repeating header rows across multi-page printouts
Keeping First row is a header checked repeats your column labels automatically at the top of page 2 and every page thereafter. Readers never have to flip back to page 1 to remember which numeric column holds net totals versus tax amounts.
If a table spans dozens of pages for board packets or client audits, pairing repeating headers with consistent page numbers makes cross-referencing fast. You can jump straight to numbering pages from the completion panel after generating the PDF.
Every generated table cell wraps long text cleanly within column boundaries rather than truncating numbers or overflowing off the right margin. That layout discipline ensures financial totals and account codes stay readable when printed on physical paper.
How does automatic delimiter detection handle commas and semicolons?
Automatic detection scans up to 10 non-empty rows within the first 10,000 characters and scores commas, semicolons, tabs, and pipes by how consistently each appears outside double quotes. The separator with the highest consistency and column count wins, preventing European semicolon exports from collapsing into a single column.
Under IETF RFC 4180 CSV Format Specification, standard CSV files use commas, yet localized spreadsheet exports frequently substitute semicolons when commas act as decimal separators. When your downstream workflow needs structured API payloads rather than printouts, use CSV to JSON on the same delimited text.
Scoring consistency across multiple rows ensures a stray comma inside a single quoted address never tricks the parser into choosing the wrong separator. Even pipe-delimited database dumps and tab-separated TSV exports render into aligned columns immediately.
| Delimiter | Typical source | Auto-detected? | Common edge case |
|---|---|---|---|
Comma , |
US/UK Excel, SQL exports, APIs | Yes | Numeric fields with thousands commas must be quoted |
Semicolon ; |
European Excel locales | Yes | Standard when decimals use commas |
Tab \t |
TSV files, clipboard copies | Yes | Preserves internal commas without quoting |
Pipe | |
Legacy ERP and log dumps | Yes | Often used when text contains commas and semicolons |
RFC 4180 quoting, UTF-8 BOM cleanup, and unclosed quote warnings
Real-world exports often carry invisible encoding markers or truncated quotes that silently corrupt naive line-splitting parsers. Handling both quirks up front ensures clean PDF cells without manual text-editor cleanup.
Stripping UTF-8 Byte Order Marks from Excel exports
Desktop Excel frequently prepends an invisible U+FEFF Byte Order Mark so Windows opens UTF-8 CSVs cleanly, as explained in the Unicode Standard UTF-8 Byte Order Mark FAQ. Left unstripped, that invisible character breaks header matching and leaves stray symbols in the first cell, so the parser strips U+FEFF automatically before tokenizing.
Diagnosing unclosed double-quote warnings before export
If a CSV export was truncated mid-file or contains an unescaped ", a warning banner flags the exact line where an unclosed quote begins. Fixing that stray quote before clicking Make PDF prevents hundreds of rows from collapsing into a single cell, and for billing runs you can also feed clean CSVs into a batch CSV invoice PDF generator.
Doubled double-quotes inside quoted strings ("") are unescaped cleanly according to RFC 4180 rules. Multiline addresses wrapped inside quotes stay together inside their intended table row instead of splitting into broken extra rows.
Page size, automatic landscape orientation, and text sizing
Choosing the right sheet geometry keeps dense numeric tables legible without awkward horizontal clipping. Adjusting orientation and font size takes one click before rendering.
Why wide tables over 5 columns switch to landscape
Using the MDN Web Docs Navigator.language Property, Page size defaults to US Letter for en-US and en-CA locales and A4 elsewhere. When Orientation is set to Automatic, any table exceeding 5 columns rotates to landscape automatically so columns keep breathing room.
Choosing 7 pt, 9 pt, or 11 pt text for dense columns
Text size defaults to Medium (9 pt), with Small (7 pt) available for wide ledgers and Large (11 pt) for compact 2-to-4 column lists. If your source data lives in documentation rather than CSV, try our tool to keep wide Markdown pipe tables aligned on landscape PDFs.
Tip: For 8-to-12 column exports, pair Automatic (or Landscape) orientation with Small (7 pt) text size. Checking the row and column summary above the preview confirms every delimiter split cleanly before generating the PDF.