Convert & Encode

To pin down exactly when a Unix timestamp in an API log occurred, use the timestamp converter; to break a long URL down into its query parameters one by one, use the URL parser. Both update the moment you enter a value.

Need to turn a JSON API response into a table or CSV for a spreadsheet, or the reverse — Excel data into JSON? The data converter handles 30-plus formats and also cleans up indentation or minifies the result.

Turning a blog post title into something URL-safe is what the slug generator does, tidying spaces and special characters into hyphens, while Markdown documents get a live HTML preview alongside the generated code. The encoder moves between Base64, URL and HTML encoding on one screen.

A frequent miss when reading a timestamp from an API log is timezone — a value logged as UTC can look like local time and throw your conclusion off by hours, so always check which timezone the converter is displaying. Converting JSON to CSV gets messy when the source has nested objects or arrays that don't flatten neatly into one row per line; check the indented original first to decide how much of it to convert. Turning a Korean title straight into a slug by romanizing it whole tends to produce something too long — picking two or three core keywords instead reads better for both search engines and people.