# CSV.jl "corrupts" data when a field is very large

**URL:** <https://discourse.julialang.org/t/csv-jl-corrupts-data-when-a-field-is-very-large/133513>\
**Category:** Data\
**Tags:** csv\
**Created:** [October 29, 2025, 1:31pm UTC](https://discourse.julialang.org/t/csv-jl-corrupts-data-when-a-field-is-very-large/133513 "2025-10-29T13:31:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![TimG](https://avatars.discourse-cdn.com/v4/letter/t/82dd89/32.png) [@TimG](https://discourse.julialang.org/u/TimG)\
**Post date:** [October 29, 2025, 2:11pm UTC](https://discourse.julialang.org/t/csv-jl-corrupts-data-when-a-field-is-very-large/133513/5 "2025-10-29T14:11:13Z")

</div>

Here’s another possible option:

> [@CSV.jl writing quoted strings](https://discourse.julialang.org/t/csv-jl-writing-quoted-strings/123989/15):
>
> For a CSV reader/writer robust in edgecases like that, you may try duckdb – convenient to use from Julia though [QuackIO.jl](https://juliaregistries.github.io/General/packages/redirect_to_repo/QuackIO).

Also, have you tried using CSV with `ntasks=1`. Multi-threading in CSV sometimes has some issues (e.g. with a `\n` character in a quoted string) and working single threaded can avoid these.

---

_[View the full topic](https://discourse.julialang.org/t/csv-jl-corrupts-data-when-a-field-is-very-large/133513)._