What file formats are supported?

You can paste or upload CSV, JSON, and SQL schema files. The tool can auto-detect the format, or you can manually specify it.

What is a prefix window?

The prefix window controls how many leading characters the tool examines to find abbreviation or prefix collisions. You can set it between 2 and 8 characters.

What kind of visual confusions does it detect?

It detects common typographic similarities that cause bugs, such as lowercase 'l' versus uppercase 'I', the letter 'O' versus the number '0', and 'rn' versus 'm'.

Does this tool modify my original data?

No, the tool only analyzes the field names and outputs a JSON report with collision details and rename suggestions. Your original data remains completely unchanged.

Can I use this for large database schemas?

Yes, you can paste your CREATE TABLE statements or upload a .sql file up to 10MB to analyze column names across large schemas.

Elysia Tools

Navigation

Generator

Mock Data Prefix / Abbreviation Conflict Detector

Detect visually confusing field names and prefix collisions in CSV, JSON, or schema inputs, then suggest clearer renames

Details

What this tool helps you do

Paste CSV headers, JSON mock data, or a database schema, and the tool will collect field names, normalize visually confusing patterns, and surface collisions such as l vs I, O vs 0, rn vs m, or overlapping prefixes that can cause test-data bugs.

How to use it:

Input Data / Schema: paste CSV, JSON, or CREATE TABLE text
Input File: upload a local CSV, JSON, or schema file
Input Format: use auto-detect or force csv / json / schema
Prefix Window: controls how many leading characters to use when looking for abbreviation/prefix collisions

What it reports:

visual-confusion groups
prefix collisions
clearer rename suggestions

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Prepared example runs

Click an example to fill the form automatically. File inputs still need an upload.

1 examples

Find visually confusing mock-data fields before they leak into tests

Detect collisions like userId vs user1d and c0de vs code so test fixtures and snapshots stay readable.

{"summary":{"fields":6,"groups":2},"conflicts":[{"normalizedKey":"userid","fields":["userId","user1d"]}]}

Inputs

Set the required fields, then run the tool.

4 options

FilesUpload source files for this workflow.1

Input FilefileOptional

Single file max size: 10 MBSupported types: application/json, text/plain, text/csv, .json, .csv, .sql, .txt

ContentPaste or type the main input values.1

Input Data / SchematextareaOptional

SettingsAdjust formats, ranges, numbers, and modes.2

Input FormatselectOptionalPrefix WindownumberOptional

Result

Ready for a run

Run the tool to preview files, text, structured data, or streamed output here.

Samples

Mock Data Prefix / Abbreviation Conflict Detector

What this tool helps you do

Run this tool

Prepared example runs

Inputs

Result

Examples that match this tool

Continue with connected tools and hubs

Prepared example runs

Inputs

Result

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Fixing Confusing CSV Headers

2. Auditing JSON Mock Data for Tests

FAQ

CSV Samples

Python Samples

CouchDB Database Samples

JWT Samples

CSV to Database Migration Planner

Structured Log Analyzer

Dataset Imbalance Detector & Resampler

Time Series Anomaly Detector

JSON Schema, Mock Data, and API Fixture Generators

JSON Interchange and Format Translation Tools

Text Case, Encoding, and Normalization Conversion Tools

JSON Inspection, Diff, and Transformation Tools