About PartToolHub

PartToolHub is a collection of 35 single-purpose text and data tools in 6 categories, all of which run in your browser. Each one does a chore you could script in a minute but would rather not script again: joining a column into a comma list, reading the claims inside a JWT, finding the line where a JSON payload breaks.

Who builds it

I'm Parthesh Gupta (LinkedIn), and I build and maintain everything here: the conversion engines, their tests, the pages and the hosting. I work as a backend-focused software developer, which is exactly why these tools exist: most of them started as small scripts I kept rewriting for myself before I put them behind a UI. The site started on 13 September 2026 as two converters, column-to-list and list-to-column, that I wanted in a form I could bookmark, and has grown one tool at a time since. There is no team and no company behind it.

Why it exists

Most "online converter" pages send what you paste to a server, wrap the result in a page of filler, and stop at the easy cases. I wanted the opposite: a page that does the conversion on your own device, tells you exactly what it changed (the counters and status lines on every tool), and documents the awkward inputs: quotes inside values, tokens with the wrong number of segments, integers too large for JSON. Those are the cases you actually search for.

How the tools are tested

Every tool is split into a pure conversion engine with no browser code and a thin layer that wires it to the page. The engines have unit tests that run before each build; a test also checks the tool registry itself, so a page cannot ship with an over-long title, a duplicate search intent, or a missing review date. The worked example on each tool page is produced by running that tool's real engine at build time, not typed in, so the documentation cannot drift from what the tool does.

How the pages are written

The text on a tool page comes from running the tool against real and deliberately broken input and writing down what happens. I sometimes use writing tools to draft or tidy prose, but every sentence is checked against the running tool and edited by me before it is published, and each page shows the date I last did that review. If you find a claim on a page that the tool does not live up to, that is a bug: please tell me.

What happens to your data

Nothing you paste is uploaded, and not as a policy choice you have to trust: the site is a set of static files with no server component, so there is nowhere for the text to go. You can load a tool, disconnect from the internet, and keep using it. The privacy policy covers the two third-party services that do run on the page, advertising and analytics, and what they can see.

How the site is funded

The plan is to cover hosting and development with display advertising through Google AdSense. The account is currently under review, so no ads are running yet and I'm covering costs myself in the meantime. Once approved, ads will never appear above a tool or between its input and output, there will be at most two on a page, and the tools will work identically with an ad blocker on. Text you paste into a tool is never used for advertising, because it never leaves the page.

Reporting a bug or requesting a tool

The source code is public at GitHub. Open an issue with the tool name, the browser you used, a small sample of the input and what you expected. I read everything and usually reply within a few working days.

Last content review across the site: 17 October 2026.