PIXELOKAY / DATA & AI TOOLS

Data Schema Mapper

Compare two data structures, discover likely field matches, customize transformations, and deliver clean, validated output—without sending a record to a server.

✦ Smart Match + optional local AI◈ JSON / CSV / TSV / JSONL✓ Conversion diagnostics↓ Mapping & data export

YOUR DATA WORKSPACE

AI Data Schema Mapper

Import → Smart Match → Review → Validate → Export

Source records—Input dataset
Target fields—Destination schema
Mapped fields—Approved transformations
Preview errors—First preview rows

01 / SOURCE

Where data comes from

INPUT

Your records to transform. Nested JSON objects are supported; arrays are kept as values.

↑Drop your source file hereCSV, TSV, JSON, JSONL · 8 MB · 10,000 records
No source loaded

Field quality summary appears after import.

02 / TARGET

Where data should go

OUTPUT

Import an example of the destination format. Field types and required status can be edited later.

↓Drop a target sample hereAt least one example record or column header
No target loaded

03 / FIELD MAPPING

Connect the right fields

Smart Match ranks field names, aliases and compatible types. Review every suggestion; nothing is silently approved.

AI suggestions are optional and require local model setup. Smart Match needs no download.
Load both datasets to begin.
Target field · output typeSource field(s)TransformationParameter / defaultReview
Load source and target data, or try the example to start.

Rules: Copy, Trim, Upper/Lowercase, Number, Boolean, ISO date, Join, Split, Constant, Multiply, Replace, Prefix, Suffix, Round. Split parameter: delimiter|index. Join parameter: separator. Multiply: numeric factor. Replace: find|replacement. Round: decimal places 0–10.

04 / VALIDATION

Test your mapping

Preview up to 100 rows with clear conversion errors. Strict mode omits invalid rows from the exported dataset.

No preview yet.
Your transformed data preview will appear here.

05 / DELIVERY

Export and reuse

All downloads are generated inside your browser. No data is sent to PixelOkay.

Spreadsheet-safe CSV adds a leading apostrophe to text beginning with formula-like characters (such as + in phone numbers). Select JSON or JSONL if you need exact text-byte round trips.

Mapping files store field paths and rules, not source records. Reopen a mapping after loading matching source and target datasets.

How smart matching works

Smart Match uses deterministic field-name similarity and type compatibility without any model. Optional AI proposals run in your browser only after you explicitly load a local model. All AI suggestions require your approval and validation.

FOR DEVELOPERS, DATA TEAMS & CONTENT CREATORS

Turn mismatched columns into a repeatable workflow.

01

Compare schemas

See inferred fields and types from structured examples, including nested JSON properties.

02

Review suggestions

Build one-to-one field mappings, customize casts, and resolve missing or ambiguous matches.

03

Export with confidence

Inspect row-level conversion errors and save reusable rules for later datasets.

Frequently asked questions

Is this generative AI?

Smart Match uses deterministic local rules. Optional AI Suggest uses field paths, types and required flags, not record values, to propose unapproved mappings with a model that runs in your browser. WebLLM runtime assets load from a pinned CDN and model files download after you select a model; browser-built-in AI is experimental. Review each suggestion.

Does it support Excel spreadsheets?

Export your spreadsheet as CSV or TSV first. Native XLSX and relational joins are not currently supported.

Are data files uploaded?

Source records stay in this browser tab, and the optional AI prompt contains only field paths, types and required flags, not row values. The model runs in the browser; choosing WebLLM can load runtime files from a CDN and download model weights. No source row values are sent to an AI model.

What happens if data cannot be converted?

Conversion problems are reported by row and target field. You can choose lenient output with null values or strict output that excludes invalid rows.

Map CSV and JSON records to a target schema

Match source fields to a target structure, review transformations, and validate rows before exporting. Deterministic Smart Match is available without a model; optional AI suggestions use schema field metadata and remain unapproved until you review them.

  1. Import a source CSV, TSV, JSON or JSONL dataset, then add a target sample or header that shows the required fields.
  2. Run Smart Match or choose optional AI Suggest. Review every source-to-target path and select only supported transformations you need.
  3. Preview the first 100 rows, run full validation when ready, then export JSON, JSONL or CSV plus any issue report or reusable mapping settings.

Example: Map an order file’s customer identifier, email address and creation date to the matching target paths. Confirm the date conversion, preview sample rows, validate the complete file and download JSONL.

Limits and privacy: Imports are limited to 8 MiB, 10,000 records and 150 fields; preview shows at most 100 records. Optional AI uses field paths, types and required flags, not record values. WebLLM runtime files load from a pinned CDN and model weights download only after you select a model; browser-built-in AI is experimental. Review all suggestions and exports.

Related tools

LOCAL AI SETUP

Set up AI on this device

First, a model needs to be loaded on your device

Data Schema Mapper can use an optional local AI model to suggest source-to-target field matches. First setup may download hundreds of megabytes; your imported records are never sent to an inference server.

  1. 1. Check device
  2. 2. Download / cache
  3. 3. Initialize local AI
  4. 4. Suggest mappings
Select a compatible model. AI mapping is optional; deterministic Smart Match and exports always work without it.

Device & model resources

Measurements may be approximate
Device RAM / model memoryChecking device information…

Live system RAM, model RAM and GPU memory are not reliably exposed in browsers.

Browser website storageChecking storage…

Site-wide estimate; includes other PixelOkay tools and is not RAM.

ONE ACTION · ALL RECOGNIZED AI MODEL DOWNLOADS

Free AI model storage across PixelOkay

Scan this website origin for WebLLM and Transformers.js model caches, plus recognizable model files in other cache buckets. This includes caches from other PixelOkay tools, not only AI Chat. No site data or browser databases are cleared automatically.

Run a scan to see how many model caches can be cleared together.

Browser-native models and unknown IndexedDB/OPFS or private runtime caches may remain. Unknown application/user storage will not be deleted. Other running tools might redownload caches; close their tabs first.

Having trouble downloading or loading AI?

Old or incomplete AI model downloads may be using your browser's storage. First refresh the storage meter or try a smaller model. If setup still fails, inspect and remove recognized AI model caches with confirmation, then download again.

Only model caches are targeted. Other PixelOkay tools may need to redownload their models. Never clear all website data without exporting important chats and projects first.

Select Check compatibility to inspect the selected model and device.
Technical details and safe recovery

AI runtime: WebLLM 0.2.87 for WebGPU models; browser LanguageModel API where supported. No external inference service.

CROSS-TOOL MODEL CACHE CLEANUP

Delete recognized AI model downloads?

Only independently recognizable model caches are targeted. Other PixelOkay tools may need to redownload models. Saved projects, mapping rules, files, and browser databases are not selected, but unknown stores are not inspected or removed.

Close other AI tabs before proceeding. Browser-managed, IndexedDB, and OPFS model files may remain.