rediagram .app

About

We throw your diagram away and redraw it.

Every importer on the market tries to preserve what your file looked like. That is precisely why an imported diagram still looks imported. We keep the graph, discard the drawing, and hand you a ledger of everything we changed.

What it actually does

A .vsdx carries two different things: a graph — these boxes, these arrows, this grouping — and a drawing, which is the coordinates, fills, stroke weights and fonts somebody chose in 2019 inside Visio's default theme. Import tools treat both as content and faithfully reproduce the second one. That is the whole reason a converted diagram looks like a foreign object on your slide.

We parse out the graph and throw the drawing away. Layout is recomputed from scratch, deterministically, and painted in your tokens. The same file converted twice lands identically, and a diagram you convert today sits beside one you converted in March without the two disagreeing about what a box looks like.

Why you can check our work

Discarding things is a strong claim to make about somebody's file, so every conversion returns a fidelity ledger: what was kept, what was merged, what was collapsed, and what was dropped outright. It is part of the API response, not a footnote in the docs, and it names the losses whether or not they flatter the result.

The ledger exists because the alternative is the one thing a conversion tool must never do, which is to return something that looks finished and quietly isn't. A diagram is usually read by people who were not in the room when it was drawn. If we lost one of your edges, you need to hear it from us and not from them.

Arabic is not a translation layer

Ask for lang: ar and the layout mirrors — genuinely mirrors, so the flow runs right to left — and the labels are set on an Arabic type scale rather than Latin metrics with an Arabic face dropped in. Arabic needs more line height and different optical sizing than the Latin settings it usually inherits.

Ask for a twin and you get both languages from one graph, so the English figure and the Arabic one cannot drift apart the way two hand-maintained diagrams always do. This is the part we built for ourselves first, and it is still the part almost nothing else does.

Who is behind it

Anis Marrouchi, from Tunis. I started Noqta in 2018 as a freelance practice and it grew into a small agency shipping for clients in Tunisia, Saudi Arabia, France and the US. Rediagram came out of that work: we kept receiving diagrams in somebody else's colours and redrawing them by hand before they could go in front of a client.

It shares a codebase with claimlead.lol, which is also ours and which we mention here for the same reason we mention it there.

What we will not do

  • Report a conversion as finished when the file it produced is not there. A recorded artifact that has gone missing answers plainly that it is missing.
  • Drop part of your diagram without naming it in the ledger.
  • Train anything on the diagrams you convert.
  • Move SVG and PNG behind the paid plan. They are free today and that is not a promotion.
  • Claim a format is supported on the strength of it parsing. If it round-trips badly, the ledger will say so rather than the marketing page staying quiet.