Add your CSV file
Drop one or more .csv 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.
Restructuring .csv data as .npy changes the serialization without touching the values themselves. 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.Restructuring .csv data as .npy changes the serialization without touching the values themselves. 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.
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. For this route the practical draw is exact round trip: dtype, shape and byte order all survive and loads far faster than text and can be memory-mapped — balanced against uncompressed, so large arrays are large files, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .csv, no type information — Excel famously strips leading zeros and mangles dates on open. Switching to .npy buys you exact round trip: dtype, shape and byte order all survive, which is why it is the better fit for saving model weights, embeddings or intermediate results between processing steps. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | CSV table (.csv) | NumPy array (.npy) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Lossless — every pixel or sample is preserved exactly |
| How it stores data | 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 | the file begins with the magic byte 0x93 followed by 'NUMPY' and a two-byte version |
| Strongest at | exports from databases, CRMs, and banking systems | saving model weights, embeddings or intermediate results between processing steps |
| Weak spot | no type information — Excel famously strips leading zeros and mangles dates on open | uncompressed, so large arrays are large files |
Drop one or more .csv 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 .npy in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if NPY is selectable, the route is real and validated.
Press Convert. The restructuring is plain local parsing — your data is never posted to a server for processing.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid NPY file. Outputs keep the original filename with the .npy extension.
There is no visual quality to lose — csv is text-oriented and npy is lossless-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 .csv file is processed inside your browser tab and never uploaded. The restructuring is plain local parsing — your data is never posted to a server for processing. Close the tab and the file is gone from memory.
NumPy reads and writes it natively, and independent readers exist for JavaScript, Rust, Go, C++, Java and Julia. Novus Convert decodes one- and two-dimensional numeric arrays locally with bounded shape and dtype validation, writing JSON, CSV or XLSX, and can also produce .npy from tabular input. Object-dtype arrays are refused outright, because loading one in NumPy requires pickle and therefore code execution.
It depends on the content: the file begins with the magic byte 0x93 followed by 'NUMPY' and a two-byte version. Convert one representative file first and compare before batch-processing a large set.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .csv → .npy → .csv is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.