CSV를 JSON으로

CSV represents tabular data as comma-separated text rows, where the first row usually names the columns and every following row is a data record. JSON represents the same data as an array of objects, where each object carries the keys taken from the header row and the values taken from the corresponding row. Converting between them is a re-arrangement, not a transformation: no information is added; every cell ends up somewhere with a name attached.

Why people convert in this direction so often

CSV is what spreadsheets, exports, and legacy reports speak. JSON is what HTTP APIs, configuration files, and JavaScript runtimes speak. Converting from CSV to JSON is therefore the gluing step between data that comes from a human-edited table and code that needs to consume it as records — when a designer hands over a list of products in a spreadsheet, when an analyst exports a survey from a BI tool, or when a one-off bulk update arrives by email.

Rules that decide whether the JSON output is trustworthy

The trust you can place in the converted JSON depends on a handful of structural properties of the CSV. None of them are about a single value being right or wrong — they are about the table holding together as a table.

• The first row contains real column names — not blank cells, not duplicate names, not values that should have been data.
• Every data row has the same number of columns as the header — extra commas or missing trailing cells silently shift values.
• The delimiter is unambiguous — comma, semicolon, or tab — and is consistent across the whole file.
• Values that contain the delimiter, quotes, or newlines are quoted; embedded quotes are escaped by doubling them.
• The encoding is known and consistent — UTF-8 with or without a BOM is the safest default for cross-system handoff.

If any of these rules fails, the converter will still produce valid JSON — it just will not be the JSON you meant. Always check the first few records and one or two records from the tail before trusting the whole conversion.

이 도구 사용 방법

1. Prepare representative CSV rows that need structured JSON for APIs or tooling in CSV를 JSON으로 instead of starting with the largest or most sensitive real input.
2. Run the workflow, generate JSON arrays that preserve the row and column structure of the CSV source, and review headers, delimiters, quoting, empty cells, inconsistent row width, and whether text should stay as strings or be post-processed later before deciding the result is ready.
3. Only copy or download the result after it fits API payload drafts, config import, spreadsheet cleanup, and support investigations and no longer conflicts with this constraint: Messy CSV sources should be normalized first because malformed delimiters and quoted commas can distort the resulting JSON shape.

CSV를 JSON으로 예시

CSV를 JSON으로 예시는 작고 대표적인 CSV 샘플로 시작하는 것이 좋습니다. 생성된 JSON 구조를 먼저 확인한 뒤 같은 변환을 실제 큰 데이터에 적용할 수 있습니다.

예시 입력

name,email
Ada,ada@example.com

예상 출력

[
  {
    "name": "Ada",
    "email": "ada@example.com"
  }
]

A small CSV and its JSON equivalent

# CSV
id,name,price,inStock
1,"Notebook, A5",4.50,true
2,"Pen ""Classic""",1.20,false
3,Mug,7.00,true

# JSON
[
  { "id": "1", "name": "Notebook, A5", "price": "4.50", "inStock": "true" },
  { "id": "2", "name": "Pen \"Classic\"", "price": "1.20", "inStock": "false" },
  { "id": "3", "name": "Mug", "price": "7.00", "inStock": "true" }
]

Notice that values stay as strings in the JSON output. Type coercion ("4.50" → 4.5, "true" → true) is a separate decision because CSV has no type system to start from.

Where converting CSV to JSON is the right move

Conversion is most valuable when the next consumer of the data expects records, not rows, and when the source CSV was a one-off export rather than a long-lived data store.

• Seeding fixtures for unit or integration tests from a spreadsheet that product or QA maintain.
• Loading a one-time data update through an API that accepts JSON arrays, instead of writing a custom CSV parser.
• Bootstrapping a mock backend or a static configuration file from an exported report.
• Inspecting a CSV more carefully — JSON in a browser DevTools console is easier to navigate than a wall of comma-separated text.
• Producing a small data file for a frontend prototype where the team prefers fetch().then(r => r.json()) over a CSV parsing dependency.

Edge cases that quietly break naive conversions

Most CSV-to-JSON disasters do not look like errors at the moment of conversion. They look like JSON that parses fine but happens to be wrong. The list below is where that usually starts.

• Quoted fields with embedded newlines: real CSV allows them; many ad-hoc parsers split on \n and corrupt the row.
• Leading apostrophes (’007123’) used by Excel to force text — they survive into the JSON value and surprise downstream code.
• Locales that use a comma as the decimal separator: "3,14" looks like two fields in a comma-delimited file. Switching the delimiter to ; in the source is safer than guessing.
• Date strings without a stated format: 03/04/2024 means different days in different regions. Convert first, then normalise dates explicitly.
• Header rows that contain the delimiter or quotes — these silently produce JSON keys that you cannot reference cleanly in code.
• Very large files: streaming or chunking is required to avoid running out of memory when the converter tries to keep the entire JSON array in RAM.

How CSV and JSON differ in what they can express

실무 참고

• CSV를 JSON으로는 대표적인 CSV 샘플로 먼저 시험해 필드 이름, 중첩 구조, 빈 값, 특수 문자가 JSON 변환 후에도 유지되는지 확인한 뒤 사용하는 것이 좋습니다.
• 생성된 JSON 결과는 최종 대상 시스템에서도 다시 검토해야 합니다. 파서, 가져오기 도구, 스키마 기대치에 따라 경계 사례 처리 방식이 다를 수 있기 때문입니다.
• 이 변환이 운영 데이터에 영향을 줄 수 있다면 브라우저 출력은 초안으로 보고, 원본 입력을 함께 보관해 비교할 수 있게 하세요.

CSV를 JSON으로 참고 정보

CSV를 JSON으로의 참고 설명은 CSV 구조가 JSON 출력으로 어떻게 바뀌는지와, 재사용 전에 무엇을 검토해야 하는지에 초점을 맞춥니다.

• JSON 결과를 믿기 전에, 입력한 CSV 샘플 자체의 구조가 올바른지 먼저 확인하세요.
• 변환 후에는 중첩 배열, 혼합 값 유형, 빈 필드, 특수 문자를 우선적으로 살펴보세요.
• 생성된 JSON 출력은 후속 편집기, 파서, 가져오기 도구, 런타임에서 기대를 충족하기 전까지 초안으로 다루세요.

참고 자료

• RFC 4180: Common Format and MIME Type for CSV Files
• RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
• ECMA-404: The JSON Data Interchange Syntax