wranglify

Wranglify_

A feature complete data workbench for wonks

shown in cyberunc

a data workbench for mac and windows

Your dataset is broken.
It is also confidential.

Who puts nested JSON in a csv??

Flatten it with one click. Run it over a batch of files in a click. CSV too big to open in excel, too sensitive to paste into an online converter, and too messy for anything that only does one thing. Wranglify opens it on your own machine, shows you what is wrong, and lets you fix it one reversible step at a time. Nothing is uploaded, because there is nowhere for it to go.

signups.csv 47 rows × 8 columns 47 rows out
nameemailstatus source
    Real rows from the sample file. Click a step.

    why this exists

    Three ordinary files that nothing else will open

    Every analyst has the same three problems, and the usual answers each fail on a different one.

    01

    The spreadsheet gives up

    A spreadsheet stops at 1,048,576 rows and slows down long before that. The export you were sent has more.

    Wranglify opened a 497 MB, 5,096,070-line file and scrolled every record at the same speed at the end as at the start.
    02

    The website is not an option

    The free online converter wants an upload. The file has customer records in it, so that is the end of that conversation.

    Sandboxed, and it makes no network requests at all. Not a policy. A property you can check.
    03

    One-click tools do one thing

    The encoding is wrong AND a column holds three values AND the statuses collide by case. Four tools, four exports, four chances to lose a row.

    One pipeline, in order, reversible, and saveable as a recipe you can run again next quarter.

    power tools

    Built for people who do this all day

    Not a converter with a nice icon. The parts below are the reason people keep it open. Each is shown in a different one of the eleven themes.

    A real SQL engine, on your own machine

    Load several files as tables and join, filter, group and sort them with SQLite running locally. Every step shows the SQL it generates, so the chain is auditable rather than magic.

    • Joins across files, a read-only console, full-text search
    • Export the result as CSV, JSON, XLSX or a real .sqlite database

    shown in blackout

    Schema and INSERTs, typed from the whole file

    Turn a file into CREATE TABLE, INSERT, SELECT and UPDATE for PostgreSQL, MySQL, SQL Server or SQLite. The types come from a scan of every row, not the first ten.

    • VARCHAR sized to what is actually there, INT or BIGINT by magnitude
    • DECIMAL by observed scale, NOT NULL only where there are no nulls
    • A primary key only where the column is provably unique

    shown in antique

    Pivot by dragging, computed in SQL

    Drop fields into rows, columns and values. Totals and subtotals are their own queries, so they are measured rather than added up from what happens to be on screen.

    • Number formats per measure, heat-mapped cells
    • Out as Markdown, HTML, TSV or a styled workbook

    shown in reef

    Charts that draw what you built

    Build a pivot, press chart, and the picture is of that, aggregated in the engine rather than sampled from a preview. Drag across it to filter the data behind it.

    • Export SVG, PNG, or the Vega-Lite spec that drew it

    shown in cyberunc

    Do it once, then do it to the folder

    The pipeline saves as a recipe: a plain JSON file listing your steps in order. Authorize a folder once and apply that recipe to every file in it, from the app or from a terminal.

    • The terminal command is the same sandboxed app, not a second program
    • A dry run prints the plan before anything is written

    shown in planet

    measured, not estimated

    Numbers we had to earn

    Every figure here came out of a test in the repository, on a real file.

    5,040,000 records read from a 497 MB log, none skipped, none summarised away
    3 ms to the first screen of that file, against a 3,000 ms budget
    10 MB installed, carrying a SQL engine, a chart renderer and an XLSX writer
    0 network requests, of any kind, ever

    the part that matters

    Do not trust us. Make the machine say it.

    Anyone can write "we respect your privacy" on a page. The app ships a test that tries to smuggle data out through every channel there is and shows you each one refused, naming the rule that did it. Nothing is actually sent: the target is under .invalid, the suffix reserved so it can never exist.

    There is no account, no telemetry, no crash reporting and no server. The privacy page explains every entitlement the app holds, including the one that looks like a contradiction until you read why it is there.

    • fetch()refused by connect-src
    • XMLHttpRequestrefused by connect-src
    • WebSocketrefused by connect-src
    • tracking pixelrefused by img-src
    • <script src>refused by script-src-elem
    • form POSTrefused by form-action

    6 of 6 channels refused by the browser itself. Every route out is closed.

    where it runs

    Mac and Windows. Then Linux.

    One codebase, three targets. The engine, the pipeline and every file format are already platform-independent; what differs is the shell around them. Rather than promise dates, here is the honest state of each.

    Available

    macOS

    Universal for Apple silicon and Intel, macOS 11 and later. Sandboxed for the Mac App Store, with the folder grant and the terminal runner working inside the sandbox.

    Available Approved, arriving

    Windows

    The port is done and the Microsoft Store listing is approved. Windows 10 version 1809 and later, x64 and ARM64. It ships as a packaged desktop app, so the folder grant, batch runs and the terminal command all work exactly as they do on the Mac.

    Planned

    Linux

    Next. Same shared core again, so the remaining work is packaging and the desktop integration rather than the product itself.

    Open the file nobody else will.

    Free in your browser, right now. On your Mac or PC, in 10 megabytes, today.

    more from uncsoft

    The other end of the same idea

    Tools that do their work on your machine, sold once, with nothing to sign into. Wranglify handles the data; this is what else is on the shelf.

    cyberWriter

    A privacy-first Markdown editor for Mac. Write in plain text, watch it render live, and export to PDF, Word or HTML with no Pandoc and no round trip through anyone's server. $14.99, macOS 15 and later.

    The Architect's Toolkit

    A bundle of cyberWriter and devPad, for less than buying the two separately. Wranglify is not in this one - a bundle that includes it is on the way, and this line changes when it is approved rather than before.

    Wranglify: an offline CSV, JSON and SQLite workbench for Mac and Windows

    Wranglify is a native desktop app for Mac and Windows, for the files that defeat everything else: the 500 MB CSV that freezes the spreadsheet, the export with mojibake through every accented name, the nested JSON that is not a table yet, the extract you are not allowed to paste into a website. It profiles, cleans, joins, queries and converts them on your own machine. Nothing is uploaded, because the app has no network code to upload with.

    What it opens

    Files stream through the pipeline rather than loading whole, so the ceiling is your disk rather than your RAM. That is what makes it a viable large CSV viewer for Mac and a large CSV editor for Windows alike: files well past Excel's 1,048,576-row limit open and stay responsive.

    What it does

    Why offline is the feature

    Most data tools that look like this are websites, which means the file you were told not to email leaves the building anyway. Wranglify reads only the files and folders you hand it - sandboxed on macOS, a packaged desktop app on Windows with no network code in either. There is no account, no sign-in, no telemetry, no crash reporter and no analytics, so there is no session log of which files you opened - the pipeline you built is the only record, and it stays on your disk. The privacy page sets out exactly what that means.

    Frequently asked questions

    Do my files get uploaded anywhere?
    No. Everything runs locally, and the app is sandboxed with no network access to upload through.
    Does it work without an internet connection?
    Yes, entirely. Nothing in the app needs a connection, including the SQL engine and every export.
    How large a file can it open?
    Larger than a spreadsheet will. Files stream rather than loading into memory, so the practical limit is disk space, not RAM, and Excel's 1,048,576-row ceiling does not apply.
    Which computers does it run on?
    On the Mac, macOS 11 Big Sur and later, universal for both Apple silicon and Intel; the App Store download is about 3.9 MB. On Windows, version 1809 and later, x64 and ARM64. Same engine and same file formats on both.
    Is it a subscription?
    No. It is a one-time purchase - $19.99 on the Mac App Store - with no in-app purchases and nothing to renew.
    Is there a free version?
    Yes. unfckr.app is the same engine running in your browser, free and with no sign-up. The desktop app adds the folder grant, the command-line runner, and native file handling.
    Is there a Windows or Linux version?
    Windows is done and its Microsoft Store listing is approved. Linux is planned after it. The engine, the pipeline and every file format are already platform-independent; what differs is the shell around them.