Worldwide

Converters

Unit math, timezone offsets, JSON reshaping, and image re-encoding run in this tab. No upload step. (Currency conversion is better left to Google Search — we do not ship a weaker copy of that.)

What people actually convert

A call across three timezones where "3pm my time" needs to become three other people's calendars. Inches to millimetres on a drawing spec that a fabricator in a different country will read literally. A JSON API response dumped into CSV because the spreadsheet a finance team insists on refuses nested objects. A JPEG that needs to lose weight before Slack or a job application portal rejects the upload.

Methodology — where the numbers come from

Units and timezones: pure local arithmetic using standard conversion factors (SI-defined where applicable) and the IANA timezone database baked into the browser's Intl APIs, so DST transitions are handled the same way your OS clock handles them — no hardcoded offset table to go stale.

JSON→CSV and image tools: the JSON converter flattens nested objects into dot-notation columns (a nested address.city becomes a address.city header) rather than silently dropping structure; deeply nested or array-heavy JSON will produce wide, ugly CSVs because that is an honest representation of data that doesn't belong in a flat table. Image compression re-encodes at a chosen quality/dimension using the Canvas API; format conversion re-draws the decoded bitmap into the target container.

Worked example

15:00 IST on a weekday is mid-morning on the US East Coast when DST is in effect, and an hour earlier when it is not. Paste the same local time into the timezone converter for New York and London before you send the invite — "3pm my time" without a zone is how meetings get double-booked.

Honesty

These converters do not need the network to do their job. If your browser's timezone database is outdated, DST edges can disagree with a freshly updated OS; that is a browser limitation, not a silent upload.