Online developer utilities
Nicxro is a small set of browser-based helpers I built because I kept needing the same things: pull metadata from a clip without installing software, turn messy JSON into typed shapes, and sanity-check breakpoints before shipping.
Each utility does one job clearly—whether you need a video metadata extractor for a single clip, JSON to TypeScript (or other targets) from a sample payload, or website testing tools that compare breakpoints without spinning up a device lab.
Paste a link and extract detailed metadata from videos across platforms—codec hints, dimensions, duration-style fields when exposed, and other structured details the host makes available.
A JSON converter tool that turns raw JSON into shapes you can actually use—TypeScript types and interfaces, Dart classes, and other developer-friendly formats without hand-typing the boilerplate.
A responsive design tester that previews your site across multiple device frames side by side so you can spot overflow, tap targets, and awkward line breaks before they reach users—handy when you want lightweight website testing tools without installing simulators.
Nicxro keeps these developer utilities online so you can open a tab, finish the task, and move on—no installer, no ceremony.
Nicxro started as a place to park tools I was tired of rebuilding in one-off scripts. I ship software for a living, and most days I want a button that does the thing—extract metadata, convert JSON, eyeball a layout—without signing up for another platform or wading through a marketing page.
Nothing here pretends to be an enterprise suite. The goal is narrower: sensible defaults, readable output, and pages that load fast enough that you are not embarrassed to share a link in a chat thread. When something breaks because a host changed their response shape, I fix it and note what changed.
If a tool saves you twenty minutes this week, it did its job. Feedback is welcome; I read email when I am not deep in a release week.
You already have enough tabs open. These pages exist because I wanted the same qualities I look for in tools I did not write: fast, direct, and easy to trust with a copy-paste workflow.
01
Heavy dashboards have their place. These pages are not that. Assets stay lean, images are used sparingly, and the layout avoids pointless reflows so reading stays stable as content streams in.
02
One primary action per screen where possible. You should not need a tour to extract metadata or convert JSON—the interface gets out of the way after a single glance.
03
Output is meant to paste into an editor: types you can rename, tables you can scan, frames you can compare. The kind of small quality-of-life details you notice when you are actually shipping.
04
If it does not help you finish a task, it probably is not here. That means fewer surprises, less UI noise, and a smaller footprint for both you and whoever maintains the codebase.