Issue
Sign In
StepCodex FeaturedStepCodex Reviews
Notion Docs

Convert Excel and JSON. Free online tool, no login, no sign-up.

LocalPersonal data security

Loading Tool Engine

Usage Guide & Tech FAQ

Usage Guide

  1. Confirm supported extensions; decrypt/save copies if macros or passwords block parsing.
  2. Pick sheet/range and skip legend rows/merged title blocks so notes don’t become fields.
  3. Align the “first row is header” toggle with the sheet; map column names manually if absent.
  4. Long numeric IDs may become scientific notation—set text format in Excel before export when needed.
  5. Dates may become serial numbers or ISO strings—match backend timezone/format contracts.
  6. Blank rows/columns change array shapes; clean templates before converting.
  7. For many sheets, convert separately and merge downstream, or consolidate via formulas first.
  8. Sample ~20 rows to validate typing before running the full sheet to avoid huge JSON freezes.
  9. Re-validate with schemas or TS types before committing outputs to repos.
  10. Redact PII/salary data; parsing stays local unless the page states otherwise.
  11. Read the title and description first to confirm this utility matches your task (avoid using the wrong tool and misinterpreting output).
  12. Paste or type input in the editor; if a sample/template is provided, load it first to learn the expected output shape.

Related Tech Knowledge

  • XLSX is ZIP+XML; browser parsers (e.g., SheetJS) may not match every Excel feature.
  • Displayed formatting can differ from stored cell types—trust the stored value for inference.
  • Merged cells need a policy: fill from top-left or emit nulls for covered cells.
  • Paste values instead of formulas before conversion to avoid exporting formula text.
  • Rich text/newlines inside cells usually flatten to plain strings with `\n`.
  • Huge sheets stress memory; millions of rows belong in Python/pandas or ETL tools.
  • Locale affects decimal separators; agree on assumptions for international teams.
  • Compared to CSV, Excel carries more type hints but can still misread numeric-looking text.
  • Prefer Excel Tables with stable names over hard-coded cell coordinates in automation.
  • Output is data-only—Excel validations/dropdowns aren’t carried into JSON automatically.
  • Core parsing and computation run in your browser; by default your raw business payload is not persisted to this site’s servers (see on-page privacy notes).
  • The pipeline is typically: read input → parse (lexical/syntactic/structured) → transform → render; failures aim to be diagnosable.