About

Who runs this

DevCvt is a solo project by a developer who likes building small, enjoyable things. These tools exist because the alternatives are slow, ad-heavy, and in the worst documented cases quietly keep a copy of whatever you paste.

I write software for a living and spend a lot of my own time building things that are fun to make and pleasant to use — this site is one of them. There is no company behind it, no team and no roadmap: the tools here are the ones I personally got tired of not having a clean version of.

That also shapes what gets built. Features arrive when they scratch a real itch, tools get rewritten when the output is wrong, and nothing ships behind a login. Bugs reported through the contact page are read by the same person who wrote the code, usually within a couple of days.

Why these tools exist

The developer tools people reach for most often are the small ones: reformat a payload, decode a token, work out when a cron job fires next. The sites that host them have drifted in the same direction over the years — more ad networks per page, more interstitials, more "upgrade to export", and in the worst documented cases, a server-side copy of everything users pasted in.

DevCvt is the opposite bet. Reformatting JSON or decoding a timestamp is a pure string transformation; there is nothing worth computing on a server, so nothing here does. That single decision removes an entire category of risk for the person using the tool, and it makes the pages fast as a side effect.

What "local processing" means in practice

It is a constraint on the code, not a slogan. Tool modules are plain functions with no network access, and there is no backend that could receive a payload even if a bug tried to send one. You can confirm this in three ways:

1. Watch the network. Open developer tools, switch to the Network panel, and use any tool. No request carries your input.
2. Go offline. Turn off your connection and keep working. Every tool still functions.
3. Read the policy. The privacy policy lists every script the site loads and exactly what each one can see. There is one third-party script, and it is the advertising tag.

How the site is funded

Advertising. There is no paid tier, no feature held back, and no login wall. Ads sit between the tool and the guide below it, never inside the working area, and they receive nothing you type. If you would rather not see them, an ad blocker does not break anything here — every tool works exactly the same.

Technology

The site is a static build: pre-rendered HTML, one stylesheet, self-hosted fonts, and a small JavaScript bundle per tool. No framework runs in your browser, no cookie is set by the site itself, and the only stored value is your light/dark preference.