<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Benjamin</title>
    <description>The latest articles on DEV Community by Benjamin (@developer_tech).</description>
    <link>https://dev.to/developer_tech</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4065809%2F03fc1a03-b797-4880-a3f1-bc0e0e819834.png</url>
      <title>DEV Community: Benjamin</title>
      <link>https://dev.to/developer_tech</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/developer_tech"/>
    <language>en</language>
    <item>
      <title>I benchmarked CSV vs JSON on 200k rows so you don't have to</title>
      <dc:creator>Benjamin</dc:creator>
      <pubDate>Thu, 06 Aug 2026 12:01:48 +0000</pubDate>
      <link>https://dev.to/developer_tech/i-benchmarked-csv-vs-json-on-200k-rows-so-you-dont-have-to-1m0p</link>
      <guid>https://dev.to/developer_tech/i-benchmarked-csv-vs-json-on-200k-rows-so-you-dont-have-to-1m0p</guid>
      <description>&lt;p&gt;Most "CSV vs JSON" comparisons are vibes. &lt;a href="https://instant-data-converter.vercel.app/guides/csv-vs-json" rel="noopener noreferrer"&gt;Here are real numbers, measured on a real dataset.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; 200,000 rows x 12 columns, Node v22.18.0, no streaming tricks.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;CSV file size&lt;/td&gt;
&lt;td&gt;20.5 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;JSON file size&lt;/td&gt;
&lt;td&gt;49.3 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Size ratio&lt;/td&gt;
&lt;td&gt;CSV is 2.4x smaller&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CSV to JSON speed&lt;/td&gt;
&lt;td&gt;~75,234 rows/sec&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;JSON to CSV speed&lt;/td&gt;
&lt;td&gt;~70,908 rows/sec&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Round-trip&lt;/td&gt;
&lt;td&gt;Lossless&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Why JSON is bigger:&lt;/strong&gt; repeated key names on every object, plus escaping of quotes and non-ASCII characters. For log files and export pipelines the size gap translates directly into bandwidth and storage costs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to use:&lt;/strong&gt; JSON for APIs and nested structures; CSV for storage, spreadsheets and analytics imports. If your data is a flat table, CSV wins on size and tooling.&lt;/p&gt;

&lt;p&gt;I built a free in-browser converter that does JSON↔CSV↔TSV plus a bunch of text utilities, 100% client-side (your data never leaves the machine): &lt;a href="https://instant-data-converter.vercel.app" rel="noopener noreferrer"&gt;https://instant-data-converter.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Full guide with methodology: &lt;a href="https://instant-data-converter.vercel.app/guides/csv-vs-json" rel="noopener noreferrer"&gt;https://instant-data-converter.vercel.app/guides/csv-vs-json&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
