Add your NPY file
Drop one or more .npy files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .npy font to .csv repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .npy font to .csv repackages the same glyphs and metrics for a different delivery target. An .npy file is a single NumPy array saved to disk: a short header describing the element type, the shape and the memory order, then the raw array bytes. It is deliberately the simplest thing that can round-trip an array exactly, and the specification fits on one page.
A .csv file is a comma-separated values table: plain-text rows with commas between fields, optionally quoted. It is probably the most widely produced data format in existence, emitted by everything from banking portals to lab instruments. For this route the practical draw is supported by effectively every data tool ever written and human-readable and hand-editable in a pinch — balanced against no type information — Excel famously strips leading zeros and mangles dates on open, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .npy, uncompressed, so large arrays are large files. Switching to .csv buys you supported by effectively every data tool ever written, which is why it is the better fit for exports from databases, CRMs, and banking systems. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | NumPy array (.npy) | CSV table (.csv) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | the file begins with the magic byte 0x93 followed by 'NUMPY' and a two-byte version | fields containing commas, quotes, or newlines are wrapped in double quotes with embedded quotes doubled — the rule that breaks every naive split-on-comma parser |
| Strongest at | saving model weights, embeddings or intermediate results between processing steps | exports from databases, CRMs, and banking systems |
| Weak spot | uncompressed, so large arrays are large files | no type information — Excel famously strips leading zeros and mangles dates on open |
Drop one or more .npy files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .csv in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if CSV is selectable, the route is real and validated.
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid CSV file. Outputs keep the original filename with the .csv extension.
There is no visual quality to lose — npy is lossless-oriented and csv is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes — the .npy file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Every spreadsheet, database, and programming language handles CSV, and browsers or text editors open it as plain text. The catch is dialect drift: delimiter, encoding, and quoting choices differ enough that robust importers always offer manual overrides.
It depends on the content: fields containing commas, quotes, or newlines are wrapped in double quotes with embedded quotes doubled — the rule that breaks every naive split-on-comma parser. Convert one representative file first and compare before batch-processing a large set.
In .npy, the dtype, shape and storage order are read and reported; the format itself has no field-name or unit channel, so CSV and spreadsheet targets receive positional column headings. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .npy → .csv → .npy is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.