
10,000-Row CSV
A CSV with 10,000 data rows, for testing streaming parsers, memory handling, and import performance.
- File
- CSV · CSV · 10,000 rows
- Use case
- CSV parsingData import
Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.
Page 1 of 53; 24 results per page.

A CSV with 10,000 data rows, for testing streaming parsers, memory handling, and import performance.

Where the original view of head and shoulders portrait of an older white woman with short grey hair, plain cream background landed inside the expanded frame, as JSON: the rectangle 128,0 to 640,512 in a 768x512 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of an east asian woman with glasses, plain warm grey background landed inside the expanded frame, as JSON: the rectangle 0,128 to 512,640 in a 512x768 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of a bearded white man in his thirties, plain olive studio background landed inside the expanded frame, as JSON: the rectangle 0,0 to 512,512 in a 704x512 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of a south asian man in his fifties, plain slate studio background landed inside the expanded frame, as JSON: the rectangle 192,0 to 704,512 in a 704x512 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of a smiling white woman against a plain blue studio background landed inside the expanded frame, as JSON: the rectangle 0,0 to 512,512 in a 512x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of a young hijabi woman against a plain neutral studio background landed inside the expanded frame, as JSON: the rectangle 96,96 to 608,608 in a 704x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Where the original view of head and shoulders portrait of an older east asian man against a plain warm studio background landed inside the expanded frame, as JSON: the rectangle 64,32 to 576,544 in a 768x640 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.

Aged creditors summary for Alder Books Reconciliation. The 3 suppliers behind the 16 operating payments, grouped by expense category. The amounts due are 774.00, 617.00, 673.00 and they sum to 2064.00, which is the total of the three actual columns on the budget report.

Aged debtors report for Alder Books Reconciliation. 8 open receivables aged at 2026-09-08, each with 100.00 outstanding against an invoice of between 750.00 and 1275.00. The ageing buckets hold 0.00 current, 500.00 at 31 to 60 days and 300.00 at 61 to 90 days, summing to 800.00, the receivables line of the trial balance.

Balanced manual journal batch for Alder Books Reconciliation. 3 month-end journals of 2 lines each, 6 lines in total: an accrual, a reclassification and a prepayment release. Each batch_id balances on its own and the batch as a whole posts 339.75 of debits and the same of credits.

Bank reconciliation for Alder Books Reconciliation. All 24 statement transactions matched one for one to a cash-account ledger line, with a difference column that is 0.00 on every row. There are no unpresented items and no deposits in transit, so the book balance 10236.00 equals the statement balance 10236.00 and the reconciling difference is 0.00.

Bank reconciliation JSON for Alder Books Reconciliation. The same 24 matches as bank-reconciliation.csv with the reconciliation summary at the top: statement closing 10236.00, book closing 10236.00, nothing outstanding or unpresented and a reconciling difference of 0.00.

Bank statement CSV for Alder Books Reconciliation. 24 transactions from 2026-08-01 to 2026-08-24 in separate debit and credit columns, with a running balance. The statement opens at 5000.00 and closes at 10236.00; 8 credits total 7300.00 and 16 debits total 2064.00.

Banking reconciliation identities for Alder Books Reconciliation. 5 named identities covering the amortisation, the unfinanced arrangement fee, the covenant directions, the direct debit control sum and the two different chargeback totals, with the figures behind each. The deliberate defect and its measured 36.15 USD closing balance are listed separately.

Budget versus actual for Alder Books Reconciliation. 3 expense categories for 2026-08 with budget, actual, variance and variance percent. Budgets total 4200.00 against actuals of 2064.00, leaving 2136.00 unspent. Every actual equals the sum of the ledger postings to that expense account.

camt.053 bank statement for Alder Books Reconciliation. An ISO 20022 camt.053.001.02 BankToCustomerStatement carrying the same 24 entries as bank-statement.csv. The OPBD balance is 5000.00 and the CLBD balance 10236.00; TxsSummry declares 8 credit entries totalling 7300.00 and 16 debit entries totalling 2064.00, and Ntry elements are present for all 24.

camt.053 whose entry count does not match its entries for Alder Books Reconciliation. Well-formed XML with the same header, balances and TxsSummry as bank-statement-camt053.xml, but the final Ntry, TXN-024 for 206.00 on 2026-08-24, has been dropped. NbOfNtries still declares 24 while only 23 Ntry elements are present, and the entries now sum to 10442.00 against a CLBD balance of 10236.00.

Chart of accounts for Alder Books Reconciliation. 9 postable accounts covering assets, liabilities, equity, income and expenses, with the normal balance side declared on every row. Codes run 1000 to 5200 and every account code used anywhere in the general ledger export appears here.

Chart of accounts JSON for Alder Books Reconciliation. The same 9 accounts as chart-of-accounts.csv as a JSON array under an accounts key, with the reporting currency declared once at the top level.

COBOL copybook for the GL feed for Alder Books Reconciliation. A COBOL record description for the same 120-character layout, with PIC clauses matching gl-feed-layout.json field for field: X(n) for the alphanumeric fields and 9(12)V99 for the two amount fields, which is where the two implied decimal places are declared. Comment lines carry the column ranges.

Credit application JSON for Alder Books Reconciliation. The same application as an object, with each financial summary row keeping the source string that names the file and column it came from. The connected facility is a nested object rather than a string, so a reader can tell that the existing borrowing belongs to a different entity.

Fixed-width general ledger feed for Alder Books Reconciliation. 66 records of exactly 120 characters each, the shape a legacy banking or ERP feed still arrives in. Amounts are unsigned cents, zero filled and right justified in a 14-character field, so 5000.00 is written as 00000000500000. Text fields are space padded and truncated at their declared width. There is no delimiter and no header row; the column map is gl-feed-layout.json.

Fixed-width GL feed column map for Alder Books Reconciliation. The documented column map for gl-feed-fixed-width.txt: 7 fields with 1-based start position, length, end position and type, adding up to the declared 120-character record. It also states the padding rules and that amounts carry two implied decimal places.