# inbrowser.sh — full reference for LLMs Private Markdown converter and developer tools that run locally in your browser. Every tool below runs 100% in the user's browser. No upload, no signup, no tracking cookies. Free and open in scope. Total tools: 32. Authoritative URL: https://inbrowser.sh ## Primary Markdown conversion module The primary inbrowser.sh workflow is To Markdown: a browser-side converter for preparing Markdown from local files, exports and pasted content. Main tool: https://inbrowser.sh/to-markdown Supported local inputs: HTML, saved webpages, DOCX, XLSX/XLS, CSV, TSV, PPTX, JSON, PDF, RSS/XML, RTF, TXT and existing Markdown. Privacy boundary: file conversion runs in the browser; file contents do not need to be uploaded to inbrowser.sh. Quality boundary: PDF and PPTX conversion are best-effort text extraction workflows; layouts, tables, columns, images and speaker notes may need manual cleanup. URL boundary: live URL-to-Markdown requires a server-side fetcher because browsers enforce CORS; saved HTML converts locally today. Important Markdown pages: - HTML to Markdown Converter: https://inbrowser.sh/html-to-markdown — Convert HTML files or pasted HTML to clean Markdown locally in your browser. No upload, no signup. - PDF to Markdown Converter: https://inbrowser.sh/pdf-to-markdown — Extract text from PDF files and convert it to Markdown in your browser. Best-effort, no upload. - DOCX to Markdown Converter: https://inbrowser.sh/docx-to-markdown — Convert DOCX Word documents to Markdown locally with Mammoth and Turndown. No upload. - Word to Markdown Converter: https://inbrowser.sh/word-to-markdown — Convert Microsoft Word DOCX files to Markdown in your browser. Private, no-upload workflow. - PPTX to Markdown Converter: https://inbrowser.sh/pptx-to-markdown — Extract slide text from PPTX files into Markdown sections locally in your browser. - PowerPoint to Markdown Converter: https://inbrowser.sh/powerpoint-to-markdown — Convert PowerPoint PPTX slide text to Markdown locally, grouped by slide. - XLSX to Markdown Table Converter: https://inbrowser.sh/xlsx-to-markdown — Convert Excel XLSX worksheets to GitHub-flavored Markdown tables locally in your browser. - Excel to Markdown Converter: https://inbrowser.sh/excel-to-markdown — Convert Excel XLSX or XLS sheets to Markdown tables in your browser. No upload required. - CSV to Markdown Table Converter: https://inbrowser.sh/csv-to-markdown — Convert CSV or TSV data to GitHub-flavored Markdown tables locally in your browser. - JSON to Markdown Converter: https://inbrowser.sh/json-to-markdown — Convert JSON arrays to Markdown tables or format JSON as fenced Markdown code blocks locally. - Notion to Markdown Converter: https://inbrowser.sh/notion-to-markdown — Convert exported Notion HTML, CSV or Markdown content with a private browser-side workflow. - Google Docs to Markdown Converter: https://inbrowser.sh/google-docs-to-markdown — Convert a downloaded Google Docs DOCX or HTML export to Markdown locally in your browser. - RTF to Markdown Converter: https://inbrowser.sh/rtf-to-markdown — Extract readable text from RTF files and save it as Markdown locally in your browser. - RSS to Markdown Converter: https://inbrowser.sh/rss-to-markdown — Convert RSS or Atom XML feed files to Markdown outlines locally in your browser. - URL to Markdown Converter: https://inbrowser.sh/url-to-markdown — Learn the safe URL to Markdown workflow. Live URL fetching needs a server; saved HTML converts locally. - Webpage to Markdown Converter: https://inbrowser.sh/webpage-to-markdown — Convert saved webpage HTML to Markdown locally, with live URL conversion planned server-side. - Image to Markdown OCR Workflow: https://inbrowser.sh/image-to-markdown — Prepare image text for Markdown with OCR, then convert or edit the extracted text. Direct OCR is planned. --- ## JSON Formatter URL: https://inbrowser.sh/json-formatter Category: JSON Keywords: json formatter, json validator, json beautifier, json minify, pretty print json JSON Formatter is a tool that beautifies, minifies, and validates JSON documents. Use it when you need to read API responses, lint a config file, or compress JSON before shipping it. Example: Input → {"name":"inbrowser.sh","ok":true} Output → { "name": "inbrowser.sh", "ok": true } Note → Two-space indent by default; toggle Minify to compact in one line. Steps to use: 1. Paste your JSON into the input area on the left. 2. Pick Beautify or Minify; indentation is configurable. 3. Copy the output, or fix errors highlighted in red. Common questions: Q: Is this JSON formatter safe to use with sensitive data? A: Yes. All parsing and formatting happens entirely in your browser. Nothing is uploaded to a server. Q: Does it support JSON5 or comments? A: No. The formatter follows the strict JSON specification (RFC 8259). Comments and trailing commas are reported as errors. Q: What is the largest JSON I can format? A: There is no hard limit, but browsers slow down above ~10MB. For huge files prefer a CLI like jq. Q: Can I copy the formatted result? A: Yes — every output panel has a one-click Copy button. --- ## JSON to CSV URL: https://inbrowser.sh/json-to-csv Category: JSON Keywords: json to csv, csv to json, json csv converter JSON to CSV converts an array of objects into a flat CSV table; CSV to JSON parses tabular data back into JSON. Useful when moving data between spreadsheets and APIs. Example: Input → [{"id":1,"name":"Ada"},{"id":2,"name":"Bo"}] Output → id,name 1,Ada 2,Bo Steps to use: 1. Paste your JSON array (or CSV) into the input panel. 2. Pick the direction: JSON→CSV or CSV→JSON. 3. Copy the converted output. Common questions: Q: Does it handle nested JSON? A: Nested objects are stringified into a single cell. Flatten your data first for full column expansion. Q: Is my data uploaded anywhere? A: No. Conversion runs locally via PapaParse in your browser. Q: What delimiter is used? A: Comma by default; the CSV is RFC 4180 compatible. --- ## JSON ↔ YAML URL: https://inbrowser.sh/json-to-yaml Category: JSON Keywords: json to yaml, yaml to json, yaml converter JSON to YAML converts between two of the most common configuration formats. Handy for Kubernetes manifests, CI configs, or anywhere YAML and JSON coexist. Example: Input → {"db":{"host":"localhost","port":5432}} Output → db: host: localhost port: 5432 Steps to use: 1. Paste JSON or YAML into the input panel. 2. Toggle direction; output updates instantly. 3. Copy the result. Common questions: Q: Which YAML spec is supported? A: YAML 1.2 via js-yaml. Q: Are anchors and tags preserved? A: Aliases are expanded; custom tags are not yet supported. Q: Is my YAML uploaded? A: No. Everything runs in your browser. --- ## Base64 URL: https://inbrowser.sh/base64 Category: Encoding Keywords: base64, base64 encode, base64 decode, base64 to text Base64 represents binary data as ASCII text. It is widely used in data URIs, JWTs, email attachments, and HTTP auth headers. Example: Input → Hello, inbrowser.sh! Output → SGVsbG8sIGluYnJvd3Nlci5zaCE= Note → UTF-8 safe; flip the URL-safe switch to get -_ instead of +/. Steps to use: 1. Paste text into the input area. 2. Pick Encode or Decode; toggle URL-safe if needed. 3. Copy the result. Common questions: Q: What is Base64 used for? A: Carrying binary data through text-only channels — email, JSON, URLs, HTTP headers. Q: Is Base64 encryption? A: No. Base64 is encoding, not encryption. Anyone can decode it. Q: What is the difference between standard and URL-safe Base64? A: URL-safe Base64 replaces +/ with -_ and may omit padding, so the result is safe in URLs and filenames. Q: Does it handle non-ASCII characters? A: Yes. Strings are encoded as UTF-8 first. --- ## URL Encode URL: https://inbrowser.sh/url-encode Category: Encoding Keywords: url encode, url decode, percent encoding, urlencode URL encoding (percent-encoding) escapes characters that are not safe inside URLs. Use it for query strings, path segments, and form data. Example: Input → hello world?q=inbrowser Output → hello%20world%3Fq%3Dinbrowser Steps to use: 1. Paste a URL or text segment. 2. Pick Encode or Decode. 3. Copy the output. Common questions: Q: What is the difference between encodeURI and encodeURIComponent? A: encodeURI preserves reserved characters like : / ? & =. encodeURIComponent escapes them, which is what you want for a single query parameter. Q: Does this run on the server? A: No. It uses the browser native encodeURIComponent / decodeURIComponent. --- ## HTML Entities URL: https://inbrowser.sh/html-entities Category: Encoding Keywords: html entities, html encode, html decode, escape html HTML entity encoding turns characters like < > & " into safe equivalents (< > & ") so they render correctly and prevent XSS when injecting user input. Example: Input →
Hello & welcome
Output → <div class="hi">Hello & welcome</div> Steps to use: 1. Paste your text or HTML. 2. Pick Encode or Decode. 3. Copy the output. Common questions: Q: Which entities does it cover? A: All named HTML5 entities plus numeric character references. Q: Is this safe for sanitizing user input? A: Encoding is one step. For full XSS protection use a sanitizer like DOMPurify in your render pipeline. --- ## JWT Decoder URL: https://inbrowser.sh/jwt-decoder Category: Crypto Keywords: jwt decoder, jwt parser, jwt debugger A JWT (JSON Web Token) is a base64url-encoded header.payload.signature triplet. This decoder splits and pretty-prints the header and payload locally so you can inspect claims and expiry. Example: Input → eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJuYW1lIjoiQWRhIn0.signature Output → Header: {"alg":"HS256"} | Payload: {"sub":"123","name":"Ada"} Note → Signature is shown but not verified — verification needs the issuer key. Steps to use: 1. Paste your JWT. 2. Read decoded header and payload. 3. Check the exp / iat hints. Common questions: Q: Does this verify the JWT signature? A: No. Signature verification needs the issuer's key. Decoding is local-only for safety. Q: Is my token uploaded anywhere? A: No. Decoding runs in your browser. Always rotate any token you paste into web tools. Q: What claims should I worry about? A: exp (expiry), iat (issued at), nbf (not before), iss, aud and sub — they govern token validity and intent. --- ## Hash Generator URL: https://inbrowser.sh/hash-generator Category: Crypto Keywords: hash generator, md5, sha256, sha1, sha512, hmac A hash function maps input of any length to a fixed-length fingerprint. SHA-256 and SHA-512 are recommended for new code; MD5 and SHA-1 are kept for legacy compatibility only. Example: Input → abc Output → SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad Note → MD5, SHA-1/256/384/512 all computed in parallel via Web Crypto API. Steps to use: 1. Type or paste your text. 2. All algorithms are computed instantly. 3. Copy the digest you need. Common questions: Q: Is MD5 secure? A: No. MD5 is broken for collision resistance. Use it only for non-security checksums. Q: Should I use SHA-256 or SHA-512? A: Both are secure. SHA-256 is faster on 32-bit hardware; SHA-512 is faster on 64-bit. Either is fine. Q: Does it support file hashing? A: Text input only in this release. File hashing is on the roadmap. --- ## UUID Generator URL: https://inbrowser.sh/uuid-generator Category: Generators Keywords: uuid generator, uuid v4, uuid v7, ulid, nanoid UUIDs are 128-bit identifiers used everywhere from database primary keys to session tokens. ULIDs and NanoIDs offer sortable or shorter alternatives. Example: Input → UUID v4, count 1 Output → 3f29c1d0-7b8c-4f5e-9c2a-1d4e8f6a3b21 Note → Pick v7 for time-ordered IDs that index well in databases. Steps to use: 1. Pick a format (UUID v4, v7, ULID, NanoID). 2. Choose how many to generate. 3. Click Generate and copy. Common questions: Q: What is the difference between UUID v4 and v7? A: v4 is fully random. v7 has a time-ordered prefix, making it index-friendly while still being unique. Q: Are these IDs cryptographically random? A: Yes. They use crypto.getRandomValues under the hood. Q: When should I use a NanoID? A: When you need shorter, URL-safe IDs while keeping low collision risk. --- ## Mock Data Generator URL: https://inbrowser.sh/mock-data-generator Category: Generators Keywords: mock data generator, test data generator, random csv generator, sql insert generator, sample json generator Mock Data Generator creates synthetic fixture rows for development, QA, seed data and demos. Generate users, orders or products, then export as JSON, CSV or SQL insert statements without sending data to a server. Example: Input → Users, 2 rows, JSON Output → [{"id":1,"full_name":"Ada Lovelace","email":"ada.lovelace1@example.com"},{"id":2,"full_name":"Grace Hopper","email":"grace.hopper2@test.local"}] Note → Also exports CSV and SQL insert statements for users, orders and products. Steps to use: 1. Choose a dataset: users, orders or products. 2. Pick JSON, CSV or SQL output and the number of rows. 3. Click Generate, review the synthetic records and copy the output. Common questions: Q: Is this generated data real customer data? A: No. The rows are synthetic placeholders for development, QA and demos. Q: Does the generator upload anything? A: No. Data generation and export formatting run entirely in your browser. Q: Can I use the SQL output directly? A: Use it as a quick fixture starter, then review table names, column names and data types before running it in any database. Q: How many rows can I generate? A: The browser tool caps output at 100 rows to keep the page responsive and easy to inspect. --- ## Regex Tester URL: https://inbrowser.sh/regex-tester Category: Web Keywords: regex tester, regular expression, regex match, regex playground Regex Tester lets you build and debug JavaScript regular expressions interactively. Matches highlight as you type, with group breakdowns and flag toggles. Example: Input → pattern: (\w+)@(\w+\.\w+), test: support@inbrowser.sh Output → Match: support@inbrowser.sh | Group 1: support | Group 2: inbrowser.sh Note → Large inputs are capped and match loops are guarded to reduce browser lockups. Steps to use: 1. Type a pattern (without the slashes) and toggle flags. 2. Paste a test string below. 3. Inspect matches and capture groups on the right. Common questions: Q: What regex flavor does it use? A: JavaScript (ECMAScript) regex via the native RegExp engine. Q: Is it safe against catastrophic backtracking? A: The tester caps input size and guards long match loops to reduce browser lockups, but complex patterns can still be expensive. Q: Can I share a pattern? A: URL sharing is on the roadmap; for now copy/paste both pattern and flags. --- ## Case Converter URL: https://inbrowser.sh/case-converter Category: Text Keywords: case converter, camelcase, snake case, kebab case, pascalcase Case Converter rewrites identifiers between programming naming conventions. Useful when porting code between languages or APIs with different style guides. Example: Input → Hello World Output → camelCase: helloWorld | snake_case: hello_world | kebab-case: hello-world Steps to use: 1. Paste your text. 2. Pick a target case from the dropdown. 3. Copy the converted output. Common questions: Q: Does it handle multi-line input? A: Yes. Each line is converted independently, preserving structure. Q: What about acronyms in camelCase? A: Consecutive uppercase letters collapse to one word (e.g. HTTPServer → httpServer). --- ## Text Diff URL: https://inbrowser.sh/text-diff Category: Text Keywords: text diff, compare text, diff viewer Text Diff highlights insertions and deletions between two text snippets. Useful for spotting subtle changes in config files, prose, or code. Example: Input → A: "The quick brown fox", B: "The quick red fox" Output → "brown" highlighted red (removed), "red" highlighted green (added). Steps to use: 1. Paste the original on the left. 2. Paste the new version on the right. 3. Differences highlight in green (added) and red (removed). Common questions: Q: Is it line-based or character-based? A: Character-based with word grouping for readable output. Q: Is my text uploaded? A: No. The diff runs in your browser. --- ## Line Tools URL: https://inbrowser.sh/line-tools Category: Text Keywords: sort lines, dedupe lines, remove duplicates, line numbers Line Tools batches the small text chores that come up daily — sorting, deduping, prepending line numbers — so you can stop dropping into a terminal for awk one-liners. Example: Input → banana\napple\nbanana\ncherry Output → apple\nbanana\ncherry (deduped + sorted ascending) Steps to use: 1. Paste your text. 2. Pick the operations you want. 3. Copy the cleaned-up output. Common questions: Q: Is sorting locale-aware? A: It uses the browser default locale via Intl.Collator. Q: Are duplicates case-sensitive? A: Yes by default; toggle "Case-insensitive" to merge by lowercase. --- ## Number Base URL: https://inbrowser.sh/number-base Category: Web Keywords: binary to decimal, decimal to hex, hex to binary, base converter Number Base Converter translates a value between binary (2), octal (8), decimal (10) and hexadecimal (16) — the four bases you meet every day. Example: Input → 255 (decimal) Output → Binary 11111111 | Octal 377 | Hex ff Note → Uses BigInt — arbitrary-precision integers supported. Steps to use: 1. Type a value into any of the four fields. 2. The other three update in sync. 3. Copy whichever you need. Common questions: Q: How large can the value be? A: It uses BigInt, so arbitrary-precision integers are supported. Q: Are negative numbers supported? A: Yes — a leading minus sign is preserved. --- ## Color Converter URL: https://inbrowser.sh/color-converter Category: Color Keywords: color converter, hex to rgb, rgb to hex, hex to hsl Color Converter shows the same color in HEX, RGB and HSL side by side. Handy when porting designs between Figma, CSS and design tokens. Example: Input → #6366F1 Output → RGB rgb(99, 102, 241) | HSL hsl(239, 84%, 67%) Steps to use: 1. Type a value in any of the inputs (e.g. #6366F1). 2. See the preview swatch update. 3. Copy the format you need. Common questions: Q: Is alpha supported? A: Yes — use 8-digit hex (#RRGGBBAA) or rgba()/hsla(). Q: Why might HSL round-trip differ? A: HSL has fewer representable colors than 24-bit RGB, so values may shift by ±1. --- ## QR Code URL: https://inbrowser.sh/qr-code Category: Generators Keywords: qr code generator, qr code, wifi qr code A QR Code is a 2D barcode that any phone camera can scan. This generator runs locally so even sensitive payloads (Wi-Fi passwords, internal URLs) stay on your machine. Example: Input → https://inbrowser.sh Output → Downloadable PNG QR code, error-correction level M. Note → Wi-Fi, vCard, and arbitrary text are also supported. Steps to use: 1. Type or paste your text/URL. 2. Pick an error correction level. 3. Download the QR as PNG. Common questions: Q: How much data fits in a QR? A: Up to ~4,000 characters at the lowest error-correction level, far less at the highest. Q: Is the QR uploaded anywhere? A: No. Generation runs locally via the qrcode library. --- ## Lorem Ipsum URL: https://inbrowser.sh/lorem-ipsum Category: Generators Keywords: lorem ipsum, placeholder text generator, dummy text Lorem Ipsum is filler text used in design mockups. Generate exactly as much as you need — by words, sentences or paragraphs. Example: Input → 3 paragraphs Output → "Lorem ipsum dolor sit amet, consectetur adipiscing elit…" (~150 words) Steps to use: 1. Pick a unit (paragraphs, sentences, words). 2. Choose a count. 3. Click Generate, then copy. Common questions: Q: Why use Lorem Ipsum? A: It avoids drawing attention to copy in a layout, so reviewers focus on visual design. Q: Can I change the output length? A: Yes. Pick words, sentences or paragraphs, then set the count before generating. --- ## To Markdown URL: https://inbrowser.sh/to-markdown Category: Markdown Keywords: to markdown, html to markdown, docx to markdown, pdf to markdown, csv to markdown, all to markdown To Markdown converts common files and pasted content into Markdown for docs, READMEs, RAG pipelines and LLM context preparation. Files are parsed in the browser, so document contents do not need to leave your device. Example: Input →

Guide

Hello inbrowser.sh.

Output → # Guide Hello [inbrowser.sh](https://inbrowser.sh). Note → Files and pasted content are converted locally; PDF output is text-only and can lose layout. Steps to use: 1. Drop a supported file or paste HTML, JSON, CSV, TSV, RSS, Markdown or plain text. 2. Choose output options such as links, images, GFM tables, heading cleanup and front matter. 3. Review the Markdown output, preview it, then copy or download a .md file. Common questions: Q: Are files uploaded to inbrowser.sh? A: No. File conversion runs client-side in your browser. The page may download parser code, but your file contents are not sent to a server. Q: Which formats are supported? A: HTML, DOCX, XLSX/XLS, CSV, TSV, PPTX, JSON, PDF, RSS/XML, RTF, TXT and existing Markdown are supported in this release. Q: How accurate is PDF to Markdown? A: PDF conversion is best-effort text extraction. Tables, columns, images and exact layout can be lossy, so review the output before using it. Q: Does it convert live web URLs? A: Live URL fetching needs a server-side fetcher because browsers enforce CORS. Use saved HTML with this client-side tool; the server URL converter is planned separately. --- ## Markdown Preview URL: https://inbrowser.sh/markdown-preview Category: Markdown Keywords: markdown preview, markdown editor, live markdown Markdown Preview renders GitHub-flavored Markdown on the fly so you can draft READMEs and comments with full visual feedback. Example: Input → # Hello\n\n**bold** and `code` Output →

Hello

bold and code

Note → Rendered HTML is sanitized with DOMPurify before display. Steps to use: 1. Type Markdown on the left. 2. See the rendered HTML on the right. 3. Copy the HTML when you are done. Common questions: Q: Is the HTML sanitized? A: Yes — output is sanitized via DOMPurify so it is safe to paste into a CMS. Q: Does it support tables and code blocks? A: Yes. GFM is enabled. --- ## Timestamp Converter URL: https://inbrowser.sh/timestamp Category: Time Keywords: unix timestamp converter, epoch time, timestamp to date, date to timestamp Unix timestamp conversion maps a number of elapsed seconds or milliseconds since 1970-01-01T00:00:00Z to a human-readable date. It is useful when debugging APIs, logs, databases and scheduled jobs. Example: Input → 1719792000 seconds Output → UTC: Mon, 01 Jul 2024 00:00:00 GMT | ISO: 2024-07-01T00:00:00.000Z Note → Seconds and milliseconds are both supported. Steps to use: 1. Paste a timestamp or type a date/time. 2. Choose seconds or milliseconds when converting from epoch time. 3. Compare UTC and local output before copying the result. Common questions: Q: What is Unix epoch time? A: Unix epoch time counts elapsed time since 1970-01-01 00:00:00 UTC. Q: How do I know if a timestamp is seconds or milliseconds? A: Current second timestamps are 10 digits; millisecond timestamps are usually 13 digits. Q: Does this upload my timestamp? A: No. Parsing and formatting run entirely in your browser. --- ## Timestamp Now URL: https://inbrowser.sh/timestamp-now Category: Time Keywords: current timestamp, unix timestamp now, epoch now, current epoch time Timestamp Now shows the current moment in the formats developers copy most often: Unix seconds, Unix milliseconds, ISO 8601, RFC 2822 and local time. Example: Input → Open the page Output → Live Unix seconds, milliseconds, ISO 8601, RFC 2822 and local time. Steps to use: 1. Open the page and watch the timestamp update once per second. 2. Use the copy button next to the format you need. 3. Use Timestamp Converter for a fixed date or historical value. Common questions: Q: Why are seconds and milliseconds different lengths? A: Seconds count whole seconds since epoch; milliseconds count thousandths of a second, so the number is longer. Q: Is the clock server-synced? A: No. It uses your browser and device clock. Q: Which timestamp should I use for APIs? A: Check the API docs. Many APIs use seconds; JavaScript Date uses milliseconds. --- ## Cron Parser URL: https://inbrowser.sh/cron Category: Time Keywords: cron parser, cron expression, crontab guru, cron next run Cron Parser explains five-field cron expressions and calculates upcoming matching times. Use it to sanity-check scheduled jobs before shipping them. Example: Input → */5 * * * * Output → Runs every 5 minutes; next run times are calculated in the browser. Steps to use: 1. Paste a five-field cron expression such as */15 * * * *. 2. Choose the IANA time zone your scheduler uses. 3. Read the plain-English explanation and review the next run times. Common questions: Q: Which cron format is supported? A: This release supports common five-field crontab expressions: minute, hour, day of month, month and day of week. Q: Does it support seconds? A: No. Six-field cron with seconds is intentionally excluded to keep results clear. Q: How are time zones handled? A: The interactive preview lets you choose an IANA time zone such as UTC, America/New_York or Asia/Tokyo, then calculates upcoming runs for that zone. --- ## Time Zone Converter URL: https://inbrowser.sh/timezone-converter Category: Time Keywords: timezone converter, time zone meeting planner, utc to local time, convert time zones Time Zone Converter turns one meeting time into multiple IANA time zones using the browser Intl API. It is useful for remote teams, release windows and support handoffs. Example: Input → 2026-06-29 09:00 UTC Output → Shows equivalent times in New York, London, Tokyo, Shanghai and other common zones. Steps to use: 1. Pick a source date, time and time zone. 2. Choose target zones from the common city list. 3. Copy the converted times with zone labels. Common questions: Q: Does it account for daylight saving time? A: Yes. Formatting uses IANA time zones through the browser Intl API. Q: Why use IANA names? A: Names like America/New_York are less ambiguous than abbreviations like EST or CST. Q: Can I convert UTC? A: Yes. UTC is included as a first-class zone. --- ## Date Difference URL: https://inbrowser.sh/date-diff Category: Time Keywords: date diff, days between dates, business days calculator, date difference calculator Date Difference calculates the interval between two dates in days, hours and minutes, with simple weekday and weekend counts for planning. Example: Input → 2026-06-01 to 2026-06-29 Output → 28 calendar days, with weekday/weekend counts. Steps to use: 1. Enter the start date and end date. 2. Read the total duration and calendar-day difference. 3. Use the weekday count as a rough business-day estimate. Common questions: Q: Are holidays excluded? A: No. Weekday counts exclude Saturdays and Sundays only. Q: Is the end date included? A: The duration is measured from the start instant to the end instant. Q: Does it run locally? A: Yes. Date math runs in your browser. --- ## Date Calculator URL: https://inbrowser.sh/date-calculator Category: Time Keywords: date calculator, add days to date, subtract days from date, business date calculator Date Calculator answers practical planning questions such as “what date is 45 days from now?” or “what is 10 weekdays after this release date?”. Example: Input → 2026-06-29 + 14 days Output → 2026-07-13, with optional weekend skipping for day calculations. Steps to use: 1. Choose a starting date. 2. Enter an amount and a unit. 3. Toggle skip weekends when you need a weekday-only estimate. Common questions: Q: How are months handled? A: Month addition uses JavaScript Date behavior and clamps through the calendar naturally. Q: Does skip weekends exclude holidays? A: No. It skips Saturdays and Sundays only. Q: Can I subtract time? A: Yes. Choose Subtract instead of Add. --- ## Countdown URL: https://inbrowser.sh/countdown Category: Time Keywords: countdown timer, time until date, days until, countdown calculator Countdown shows the remaining time until a target date using your browser clock. It is useful for release windows, launches, exams and event planning. Example: Input → Target: 2026-12-31 23:59 Output → Remaining days, hours, minutes and seconds. Steps to use: 1. Enter the target date and time. 2. Watch the remaining days, hours, minutes and seconds update. 3. Copy the target time in ISO format if needed. Common questions: Q: Does the countdown keep running in the background? A: Browsers may throttle timers in background tabs, but the displayed value catches up when the tab becomes active. Q: Which time zone is used? A: The date-time input uses your browser local time zone. --- ## ISO 8601 Converter URL: https://inbrowser.sh/iso-8601 Category: Time Keywords: iso 8601 converter, iso date validator, rfc 2822 date, date format converter ISO 8601 is the safest date format for APIs because it can include a precise time zone offset. This converter validates date strings and shows common alternatives. Example: Input → 2026-06-29T12:00:00Z Output → UTC, local, Unix seconds, Unix milliseconds and RFC-style output. Steps to use: 1. Paste an ISO 8601 or RFC 2822 date string. 2. Check the parsed UTC and local outputs. 3. Copy Unix seconds, milliseconds or normalized ISO output. Common questions: Q: What does Z mean in an ISO date? A: Z means UTC, also known as zero offset. Q: Why is my local time different from UTC? A: Local time applies your browser time zone offset to the same instant. --- ## Discord Timestamp URL: https://inbrowser.sh/discord-timestamp Category: Time Keywords: discord timestamp, discord timestamp generator, discord time format Discord timestamp tags render dates in each viewer’s local time zone. Generate the tag once and Discord handles localization for everyone in the channel. Example: Input → 2026-06-29 12:00, style R Output → Note → Discord renders the tag in each viewer’s local time zone. Steps to use: 1. Pick a local date and time. 2. Choose the Discord display style. 3. Copy the generated tag into Discord. Common questions: Q: Why use Discord timestamp tags? A: They avoid time zone confusion because Discord renders the time locally for each user. Q: What does R mean? A: R is the relative format, such as “in 2 hours” or “3 days ago”. --- ## Duration Converter URL: https://inbrowser.sh/duration-converter Category: Time Keywords: duration converter, seconds to hours, minutes to days, time duration calculator Duration Converter turns a numeric time span into seconds, minutes, hours, days and weeks. It is helpful for logs, timeouts, cache TTLs and monitoring windows. Example: Input → 90 minutes Output → 5400 seconds | 1.5 hours | 0.0625 days. Steps to use: 1. Enter a value and choose the source unit. 2. Read equivalent durations in other units. 3. Copy the human-readable summary. Common questions: Q: Does a month have a fixed duration? A: No. This converter intentionally uses fixed units up to weeks and avoids months. Q: Can I use decimals? A: Yes. Decimal values are accepted. --- ## Week Number URL: https://inbrowser.sh/week-number Category: Time Keywords: week number, iso week, day of year, week of year calculator ISO week numbers are used in planning, reporting and logistics. This calculator shows the ISO week-year, week number, weekday and day of year. Example: Input → 2026-06-29 Output → ISO week number, ISO weekday and day-of-year. Steps to use: 1. Choose a date. 2. Read the ISO week number and ISO week-year. 3. Use day-of-year for logs, reports and ordinal date references. Common questions: Q: Why can ISO week-year differ from calendar year? A: Early January dates can belong to the last ISO week of the previous year, and late December dates can belong to week 1 of the next ISO year. Q: Which day starts the ISO week? A: Monday is ISO weekday 1. --- ## Age Calculator URL: https://inbrowser.sh/age-calculator Category: Time Keywords: age calculator, birthday calculator, calculate age, days until birthday Age Calculator computes elapsed years, months and days from a birth date and shows how long remains until the next birthday or anniversary. Example: Input → 1990-01-01 Output → Elapsed years plus days until the next anniversary. Steps to use: 1. Enter a birth date or anniversary date. 2. Read the exact elapsed years, months and days. 3. Check the next anniversary date and days remaining. Common questions: Q: How are leap years handled? A: The browser calendar handles leap years when adding years and comparing dates. Q: Can I use it for anniversaries? A: Yes. Any start date works, not only birthdays. --- ## Cron preset pages Each cron preset page is static HTML with an expression, plain-English meaning, example use and related schedules. ### Cron every minute URL: https://inbrowser.sh/cron/every-minute Expression: * * * * * Meaning: Run once every minute. Example: Useful for local development checks, short polling jobs and queue consumers that need frequent wakeups. Modification tip: Change the first field to */5 to run every 5 minutes instead. ### Cron every 5 minutes URL: https://inbrowser.sh/cron/every-5-minutes Expression: */5 * * * * Meaning: Run at minute 0, 5, 10, 15 and so on every hour. Example: Common for health checks, cache refreshes and background synchronization. Modification tip: Use */15 in the minute field for every 15 minutes. ### Cron every 15 minutes URL: https://inbrowser.sh/cron/every-15-minutes Expression: */15 * * * * Meaning: Run four times per hour: at :00, :15, :30 and :45. Example: Good for periodic imports or dashboard refreshes where one-minute polling is too noisy. Modification tip: Use 0 * * * * to run once per hour instead. ### Cron every hour URL: https://inbrowser.sh/cron/every-hour Expression: 0 * * * * Meaning: Run at minute 0 of every hour. Example: Useful for hourly reports, cleanup tasks and log compaction. Modification tip: Change the hour field to */2 to run every two hours. ### Cron every day at midnight URL: https://inbrowser.sh/cron/every-day-at-midnight Expression: 0 0 * * * Meaning: Run once per day at 00:00. Example: Common for daily rollups, backups and maintenance windows. Modification tip: Use 0 9 * * * to run at 9:00 AM instead. ### Cron every day at 9 AM URL: https://inbrowser.sh/cron/every-day-at-9am Expression: 0 9 * * * Meaning: Run once per day at 09:00. Example: Useful for morning reports and business-day notifications. Modification tip: Use 0 9 * * 1-5 to limit the job to weekdays. ### Cron every Monday URL: https://inbrowser.sh/cron/every-monday Expression: 0 0 * * 1 Meaning: Run at midnight every Monday. Example: Useful for weekly digest jobs, billing checks and planning reminders. Modification tip: Change the last field to 5 for Friday or 0 for Sunday. ### Cron every weekday URL: https://inbrowser.sh/cron/every-weekday Expression: 0 9 * * 1-5 Meaning: Run at 09:00 Monday through Friday. Example: Good for workday reports, team reminders and business-hour automations. Modification tip: Change 9 to another hour to move the weekday run time. ### Cron first day of every month URL: https://inbrowser.sh/cron/first-day-of-month Expression: 0 0 1 * * Meaning: Run at midnight on the first calendar day of each month. Example: Useful for monthly billing, quota resets and reporting snapshots. Modification tip: Change the third field from 1 to 15 to run on the 15th day. ### Cron every Sunday at midnight URL: https://inbrowser.sh/cron/every-sunday-at-midnight Expression: 0 0 * * 0 Meaning: Run at 00:00 every Sunday. Example: Useful for weekly maintenance windows and summary generation. Modification tip: Use 1 instead of 0 in the weekday field to run every Monday. ### Cron every 10 minutes URL: https://inbrowser.sh/cron/every-10-minutes Expression: */10 * * * * Meaning: Run every ten minutes, at :00, :10, :20, :30, :40 and :50. Example: Useful for medium-frequency sync jobs, API polling and cache warmers. Modification tip: Use */5 for a faster cadence or */15 for a quieter schedule. ### Cron every 30 minutes URL: https://inbrowser.sh/cron/every-30-minutes Expression: */30 * * * * Meaning: Run twice per hour, at minute 0 and minute 30. Example: Good for batch imports, status snapshots and non-urgent monitoring jobs. Modification tip: Use 0 * * * * to run once per hour. ### Cron every 2 hours URL: https://inbrowser.sh/cron/every-2-hours Expression: 0 */2 * * * Meaning: Run at minute 0 every two hours. Example: Useful for cleanup jobs and sync tasks that do not need hourly execution. Modification tip: Change */2 to */4 for every four hours. ### Cron every 4 hours URL: https://inbrowser.sh/cron/every-4-hours Expression: 0 */4 * * * Meaning: Run at minute 0 every four hours. Example: Common for periodic maintenance, report refreshes and background reconciliation. Modification tip: Use 0 */6 * * * for four runs per day. ### Cron every 6 hours URL: https://inbrowser.sh/cron/every-6-hours Expression: 0 */6 * * * Meaning: Run at minute 0 every six hours. Example: Useful for quarterly-day rollups, CDN refreshes and batch checkpoints. Modification tip: Use 0 0 * * * when a daily run is enough. ### Cron every 12 hours URL: https://inbrowser.sh/cron/every-12-hours Expression: 0 */12 * * * Meaning: Run twice per day, every twelve hours. Example: Good for morning/evening summaries and twice-daily synchronization. Modification tip: Use 0 9,17 * * * to pin the two runs to business hours. ### Cron every day at noon URL: https://inbrowser.sh/cron/every-day-at-noon Expression: 0 12 * * * Meaning: Run once per day at 12:00. Example: Useful for midday reports, reminders and scheduled publishing. Modification tip: Change 12 to any 24-hour clock value. ### Cron every weekday at noon URL: https://inbrowser.sh/cron/every-weekday-at-noon Expression: 0 12 * * 1-5 Meaning: Run at 12:00 Monday through Friday. Example: Good for workday reminders, lunch-hour digests and operations checks. Modification tip: Change 12 to 9 for a morning weekday schedule. ### Cron every Friday at 5 PM URL: https://inbrowser.sh/cron/every-friday-at-5pm Expression: 0 17 * * 5 Meaning: Run at 17:00 every Friday. Example: Useful for weekly close reports, reminders and end-of-week summaries. Modification tip: Change the weekday field from 5 to 1 for Monday. ### Cron on the 15th of every month URL: https://inbrowser.sh/cron/every-month-on-the-15th Expression: 0 0 15 * * Meaning: Run at midnight on the 15th day of each month. Example: Useful for mid-month billing checks, payroll prep and account reviews. Modification tip: Change 15 to another day-of-month value from 1 to 31. ### Cron every Monday at 9 AM URL: https://inbrowser.sh/cron/first-monday-style Expression: 0 9 * * 1 Meaning: Run at 09:00 every Monday. Example: Good for weekly planning reminders, report delivery and status collection. Modification tip: Use 0 9 * * 1-5 to run every weekday at 9 AM. ### Cron every Saturday at midnight URL: https://inbrowser.sh/cron/every-saturday-at-midnight Expression: 0 0 * * 6 Meaning: Run at 00:00 every Saturday. Example: Useful for weekend maintenance, archive jobs and slow background work. Modification tip: Use 0 0 * * 0 for Sunday instead. ### Cron every 15 minutes on weekdays URL: https://inbrowser.sh/cron/every-quarter-hour-business-days Expression: */15 * * * 1-5 Meaning: Run every 15 minutes from Monday through Friday. Example: Good for workday-only queue processing, dashboards and support workflows. Modification tip: Add an hour range such as 9-17 to limit it to business hours. ### Cron every hour during business hours URL: https://inbrowser.sh/cron/business-hours-every-hour Expression: 0 9-17 * * 1-5 Meaning: Run hourly from 09:00 through 17:00 on weekdays. Example: Useful for workday reports, alert summaries and office-hours automation. Modification tip: Change 9-17 to match your local business window. ### Cron twice a day URL: https://inbrowser.sh/cron/twice-a-day Expression: 0 9,17 * * * Meaning: Run at 09:00 and 17:00 every day. Example: Useful for morning and evening summaries or twice-daily sync jobs. Modification tip: Change 9,17 to any comma-separated list of hours. ### Cron monthly at 9 AM URL: https://inbrowser.sh/cron/monthly-at-9am Expression: 0 9 1 * * Meaning: Run at 09:00 on the first day of each month. Example: Good for monthly billing, quota reset checks and executive snapshots. Modification tip: Change the day-of-month field from 1 to another calendar day. ### Cron quarterly URL: https://inbrowser.sh/cron/quarterly Expression: 0 0 1 */3 * Meaning: Run at midnight on the first day of every third month. Example: Useful for quarterly reports, financial checks and planning workflows. Modification tip: Use 1 1,4,7,10 * for explicit quarter-start months if your scheduler requires it. ### Cron yearly URL: https://inbrowser.sh/cron/yearly Expression: 0 0 1 1 * Meaning: Run at midnight on January 1 every year. Example: Useful for annual resets, yearly reporting and archival tasks. Modification tip: Change the month and day fields to target another annual date. ### Cron weekends at 10 AM URL: https://inbrowser.sh/cron/weekends-at-10am Expression: 0 10 * * 6,0 Meaning: Run at 10:00 on Saturday and Sunday. Example: Useful for weekend reports, non-business maintenance and community reminders. Modification tip: Use 1-5 instead of 6,0 for weekdays. ### Cron near the end of every month URL: https://inbrowser.sh/cron/last-day-pattern Expression: 0 0 28-31 * * Meaning: Run at midnight on days 28 through 31 each month, then let the job check whether it is the final day. Example: Useful for schedulers that do not support L syntax for the last day of the month. Modification tip: Add an in-job date check that only continues when tomorrow is day 1. ### Cron every 2 minutes URL: https://inbrowser.sh/cron/every-2-minutes Expression: */2 * * * * Meaning: Run every two minutes. Example: Useful for short polling loops, development checks and queue workers that need a frequent but not constant cadence. Modification tip: Use */5 for every five minutes or * for every minute. ### Cron every 3 minutes URL: https://inbrowser.sh/cron/every-3-minutes Expression: */3 * * * * Meaning: Run every three minutes. Example: Good for lightweight monitoring jobs where five minutes is too slow and every minute is too noisy. Modification tip: Change */3 to another step value in the minute field. ### Cron every 20 minutes URL: https://inbrowser.sh/cron/every-20-minutes Expression: */20 * * * * Meaning: Run three times per hour: at :00, :20 and :40. Example: Useful for periodic sync jobs, cache refreshes and status updates that can wait up to twenty minutes. Modification tip: Use */30 for twice per hour or */15 for four times per hour. ### Cron every 3 hours URL: https://inbrowser.sh/cron/every-3-hours Expression: 0 */3 * * * Meaning: Run at minute 0 every three hours. Example: Useful for scheduled imports, periodic cleanup and medium-frequency reporting. Modification tip: Change */3 to */6 for every six hours. ### Cron every 8 hours URL: https://inbrowser.sh/cron/every-8-hours Expression: 0 */8 * * * Meaning: Run at minute 0 every eight hours. Example: Good for three-times-per-day maintenance jobs and operational checkpoints. Modification tip: Use 0 0,8,16 * * * when you want explicit daily run hours. ### Cron every day at 1 AM URL: https://inbrowser.sh/cron/every-day-at-1am Expression: 0 1 * * * Meaning: Run once per day at 01:00. Example: Common for low-traffic maintenance, backups and daily cleanup after midnight. Modification tip: Change 1 to any 24-hour clock hour. ### Cron every day at 6 AM URL: https://inbrowser.sh/cron/every-day-at-6am Expression: 0 6 * * * Meaning: Run once per day at 06:00. Example: Useful for early-morning reports, inventory sync and preparation before the workday starts. Modification tip: Use 0 9 * * 1-5 for a weekday business-morning schedule. ### Cron every day at 5 PM URL: https://inbrowser.sh/cron/every-day-at-5pm Expression: 0 17 * * * Meaning: Run once per day at 17:00. Example: Useful for end-of-day summaries, reminder jobs and closing checks. Modification tip: Add 1-5 in the weekday field for weekdays only. ### Cron three times a day URL: https://inbrowser.sh/cron/three-times-a-day Expression: 0 0,8,16 * * * Meaning: Run at 00:00, 08:00 and 16:00 every day. Example: Good for three daily sync windows, operational snapshots and batch checkpoints. Modification tip: Edit the comma-separated hour list to choose different run times. ### Cron every weekday at 9 AM URL: https://inbrowser.sh/cron/every-weekday-at-9am Expression: 0 9 * * 1-5 Meaning: Run at 09:00 Monday through Friday. Example: Common for business-day reports, standup reminders and office-hours automations. Modification tip: Change 9 to another business-hour value. ### Cron every 5 minutes on weekdays URL: https://inbrowser.sh/cron/every-5-minutes-on-weekdays Expression: */5 * * * 1-5 Meaning: Run every five minutes from Monday through Friday. Example: Useful for workday-only polling, dashboards and support-hour processing. Modification tip: Add an hour range such as 9-17 to limit the schedule to business hours. ### Cron every hour during business hours URL: https://inbrowser.sh/cron/every-hour-business-hours Expression: 0 9-17 * * 1-5 Meaning: Run hourly from 09:00 through 17:00 Monday through Friday. Example: Useful for office-hours status updates, workday checks and team notifications. Modification tip: Change 9-17 to match your scheduler time zone and local office hours. ### Cron every weekend URL: https://inbrowser.sh/cron/every-weekend Expression: 0 0 * * 6,0 Meaning: Run at midnight on Saturday and Sunday. Example: Good for weekend maintenance, low-traffic jobs and non-business-day reporting. Modification tip: Use 1-5 in the weekday field for weekdays instead. ### Cron every Tuesday URL: https://inbrowser.sh/cron/every-tuesday Expression: 0 0 * * 2 Meaning: Run at midnight every Tuesday. Example: Useful for weekly jobs tied to Tuesday reporting, review or maintenance workflows. Modification tip: Change the weekday field to another number from 0 to 6. ### Cron every Wednesday URL: https://inbrowser.sh/cron/every-wednesday Expression: 0 0 * * 3 Meaning: Run at midnight every Wednesday. Example: Useful for midweek reporting, cleanup and reminder tasks. Modification tip: Change the weekday field to 5 for Friday or 1 for Monday. ### Cron every Thursday URL: https://inbrowser.sh/cron/every-thursday Expression: 0 0 * * 4 Meaning: Run at midnight every Thursday. Example: Good for weekly sync jobs, review prep and recurring operational checks. Modification tip: Change the weekday field to a different day number. ### Cron every Friday URL: https://inbrowser.sh/cron/every-friday Expression: 0 0 * * 5 Meaning: Run at midnight every Friday. Example: Useful for weekly close tasks, report generation and end-of-week processing. Modification tip: Use 0 17 * * 5 to run at 5 PM on Fridays. ### Cron every Saturday URL: https://inbrowser.sh/cron/every-saturday Expression: 0 0 * * 6 Meaning: Run at midnight every Saturday. Example: Common for weekend maintenance, archival jobs and low-traffic batch work. Modification tip: Use 0 10 * * 6,0 for a weekend 10 AM schedule. ### Cron every Sunday URL: https://inbrowser.sh/cron/every-sunday Expression: 0 0 * * 0 Meaning: Run at midnight every Sunday. Example: Useful for weekly summaries, maintenance windows and reset jobs. Modification tip: Use 1 in the weekday field for Monday instead. ### Cron every week URL: https://inbrowser.sh/cron/every-week Expression: 0 0 * * 0 Meaning: Run once per week, at midnight on Sunday. Example: Good for weekly reports, backups, account checks and recurring summaries. Modification tip: Change the weekday field to choose the weekly run day. ### Cron every month URL: https://inbrowser.sh/cron/every-month Expression: 0 0 1 * * Meaning: Run once per month, at midnight on day 1. Example: Useful for monthly billing, quotas, reports and housekeeping jobs. Modification tip: Change the day-of-month field from 1 to another date. ### Cron on the 15th of the month URL: https://inbrowser.sh/cron/15th-of-month Expression: 0 0 15 * * Meaning: Run at midnight on the 15th day of each month. Example: Common for mid-month billing checks, payroll prep and scheduled reports. Modification tip: Use 0 9 15 * * to run at 9 AM instead of midnight. ### Cron on the 1st of the month at 9 AM URL: https://inbrowser.sh/cron/month-1st-at-9am Expression: 0 9 1 * * Meaning: Run at 09:00 on the first day of every month. Example: Good for monthly reports that should arrive during business hours. Modification tip: Change 9 to another hour, or change 1 to another day-of-month. ### Cron every quarter URL: https://inbrowser.sh/cron/every-quarter Expression: 0 0 1 1,4,7,10 * Meaning: Run at midnight on the first day of January, April, July and October. Example: Useful for quarterly planning, financial reporting and recurring reviews. Modification tip: Edit the month list to match a different fiscal calendar. ### Cron every year URL: https://inbrowser.sh/cron/every-year Expression: 0 0 1 1 * Meaning: Run at midnight on January 1 every year. Example: Useful for annual reports, yearly resets and archive workflows. Modification tip: Change the day and month fields to target a different yearly date. ### Cron on New Year’s Day URL: https://inbrowser.sh/cron/new-years-day Expression: 0 0 1 1 * Meaning: Run at midnight on January 1. Example: Good for annual reset jobs, yearly summaries and new-year maintenance. Modification tip: Change the month field from 1 to another month for a different annual date. ## Privacy, comparison and GEO guides These pages are static HTML articles with direct answers, practical checklists and FAQ schema. ### Crontab.guru alternatives for private cron expression testing URL: https://inbrowser.sh/blog/crontab-guru-alternatives Category: Cron Summary: Compare cron expression tools and learn when to use a browser-side parser with timezone-aware next-run previews. Crontab.guru made cron expressions easier to read, but developers often need more than a one-line translation. A modern cron helper should explain the schedule, show next run times, make time zones explicit and keep test expressions in the browser. FAQ: Q: Is inbrowser.sh a drop-in replacement for Crontab.guru? A: It covers common five-field crontab expressions and adds timezone-aware next-run previews, but platform-specific cron dialects should still be checked against the scheduler documentation. Q: Does the cron parser upload expressions? A: No. The interactive parser runs in the browser. Static preset pages are rendered at build time for reference and search. Q: Which cron pages should I bookmark? A: Bookmark /cron for testing and /cron/every-5-minutes, /cron/every-weekday-at-9am or /cron/every-hour-business-hours for common reference schedules. ### Best private JSON formatters for no-upload debugging URL: https://inbrowser.sh/blog/best-private-offline-json-formatters-no-upload Category: JSON Summary: How to choose a JSON formatter that runs locally in the browser and avoids uploading API responses. A private JSON formatter should make API data readable without sending that data to a server. For many debugging tasks, formatting, minifying and validating JSON can happen entirely in the browser. FAQ: Q: Can an online JSON formatter work offline? A: A static browser-side formatter can continue to work after assets are cached, but true offline guarantees require a service worker or local tool. Q: Does no-upload mean no risk? A: No. It lowers the upload risk, but users should still avoid pasting production secrets or regulated data into unapproved pages. Q: What should I use for very large JSON files? A: For huge files, use local tools such as jq or an editor that can handle large documents without freezing the browser. ### Developer tools that do not upload your data URL: https://inbrowser.sh/blog/developer-tools-that-dont-upload-your-data Category: Privacy Summary: A guide to choosing browser-side developer utilities for JSON, JWT, Base64, hashes, regex and timestamps. The most useful developer utilities are often the smallest: format JSON, decode Base64, inspect a JWT, test a regex, generate a hash or convert a timestamp. Many of those tasks do not require a backend at all. FAQ: Q: Are browser-side tools always safer than server-side tools? A: They remove the need to upload input for simple transformations, but they do not replace internal security policy or local-only workflows for high-risk secrets. Q: How can I confirm a tool does not upload input? A: Use the browser network panel with a harmless sample and look for POST or fetch requests that include your pasted content. Q: Which inbrowser.sh tools are most privacy-sensitive? A: JSON Formatter, JWT Decoder, Base64, Hash Generator, Regex Tester and Timestamp tools are common places where users paste internal snippets. ### Online vs local developer tools: where does pasted data go? URL: https://inbrowser.sh/blog/online-vs-local-developer-tools-data-flow Category: Privacy Summary: Understand the data-flow difference between upload-based utilities, browser-side tools and local command-line workflows. “Online tool” can mean very different things. Some tools upload input to a backend, some run entirely in the browser after the page loads, and some are installed locally. The data-flow difference matters more than the label. FAQ: Q: Can a browser-side tool still load ads or analytics? A: Yes. Browser-side processing describes where the pasted input is transformed. Users should still review page scripts, network requests and the site privacy policy. Q: When should I avoid web tools entirely? A: Avoid web tools for production secrets, private keys, regulated data and any value that would require incident response if exposed. Q: Why does inbrowser.sh emphasize static HTML? A: Static HTML makes tool explanations, examples, FAQs and privacy boundaries visible to users and crawlers without requiring JavaScript execution. ### Why client-side developer tools are safer for everyday debugging URL: https://inbrowser.sh/blog/why-client-side-developer-tools-are-safer Category: Privacy Summary: A practical guide to when browser-only JSON, Base64, JWT and text tools are safer than upload-based utilities. Developer tools often handle data that is not meant to become public: API responses, JWT payloads, staging URLs, internal IDs, configuration snippets and draft documentation. A client-side tool does not automatically solve every privacy problem, but it removes one of the biggest risks: sending the input to a server you do not control. ### A JSON formatting checklist before sharing API data URL: https://inbrowser.sh/blog/json-formatting-checklist-before-sharing-api-data Category: JSON Summary: How to clean, inspect and safely share JSON examples in bug reports, documentation and support tickets. JSON is easy to copy and surprisingly easy to overshare. Before pasting an API response into a ticket, docs page or chat thread, it is worth taking a minute to format it, remove sensitive fields and verify that the remaining sample still demonstrates the issue. ### How to debug JWT payloads without leaking secrets URL: https://inbrowser.sh/blog/how-to-debug-jwt-payloads-without-leaking-secrets Category: Security Summary: A practical workflow for inspecting JWT headers and claims while avoiding accidental exposure of production tokens. JWTs are convenient because they carry structured claims in a compact string. They are also easy to mishandle. A token copied into a chat, ticket or random decoder may contain account identifiers, scopes, tenant names and expiry details. Debugging a JWT safely means separating what you need to inspect from what you should never share. ### Choosing the right identifier: UUID v4, UUID v7, ULID or NanoID URL: https://inbrowser.sh/blog/choosing-the-right-identifier-uuid-ulid-nanoid Category: Generators Summary: A practical comparison of UUID v4, UUID v7, ULID and NanoID for databases, URLs, logs and distributed systems. Identifier formats look interchangeable until they appear in a database index, a URL, a log line or a support ticket. UUID v4, UUID v7, ULID and NanoID can all be good choices, but they optimize for different tradeoffs. ### Markdown preview safety for documentation workflows URL: https://inbrowser.sh/blog/markdown-preview-safety-for-documentation-workflows Category: Markdown Summary: How to preview Markdown for READMEs, docs and support replies without introducing unsafe HTML or broken formatting. Markdown is the working language of READMEs, changelogs, issue templates and internal runbooks. A live preview helps catch formatting mistakes early, but documentation workflows also need a safety check: Markdown can contain links, raw HTML, code blocks and copied snippets that deserve review before publishing. ## No-upload and offline intent pages These pages target specific privacy-oriented search intents and canonicalize to themselves. ### JSON Formatter With No Upload URL: https://inbrowser.sh/json-formatter-no-upload Parent tool: https://inbrowser.sh/json-formatter Summary: Format, validate and minify JSON locally in your browser. No upload, no account and no server-side paste history. Example input: {"status":"ok","items":[1,2]} Example output: { "status": "ok", "items": [ 1, 2 ] } Q: Does this page upload JSON to a server? A: No. The linked formatter runs in the browser and does not need to post your JSON to a backend. Q: Can I use it for production secrets? A: Avoid pasting production secrets into any web page. Use local approved tools for credentials, private keys and regulated data. Q: Is the canonical URL this variant page? A: Yes. This page targets the no-upload JSON formatting search intent and links back to the main formatter. ### Format JSON Locally in Your Browser URL: https://inbrowser.sh/format-json-locally Parent tool: https://inbrowser.sh/json-formatter Summary: Local browser-side JSON formatting for API responses, config snippets and examples. Pretty-print without uploading data. Example input: {"user":{"id":123,"active":true}} Example output: { "user": { "id": 123, "active": true } } Q: What does local JSON formatting mean? A: It means the formatter uses browser JavaScript to parse and format the JSON instead of sending the input to a remote API. Q: Does local formatting work for huge files? A: Browsers can slow down on very large JSON. For huge files, use a local CLI such as jq. Q: Where should I go for the interactive tool? A: Use the main JSON Formatter page at /json-formatter. ### Offline Base64 Decode URL: https://inbrowser.sh/offline-base64-decode Parent tool: https://inbrowser.sh/base64 Summary: Decode Base64 text in your browser with no upload. Useful for headers, data snippets and UTF-8 strings. Example input: SGVsbG8sIGluYnJvd3Nlci5zaCE= Example output: Hello, inbrowser.sh! Q: Is Base64 decoding encryption? A: No. Base64 is encoding, not encryption. Anyone with the string can decode it. Q: Does decoding happen on a server? A: No. The Base64 tool decodes in the browser. Q: Can it decode URL-safe Base64? A: Yes. The main Base64 tool includes a URL-safe option. ### Client-Side JWT Decoder URL: https://inbrowser.sh/client-side-jwt-decoder Parent tool: https://inbrowser.sh/jwt-decoder Summary: Decode JWT header and payload locally in your browser. No upload and no server-side token processing. Example input: eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJyb2xlIjoiYWRtaW4ifQ.signature Example output: Header: {"alg":"HS256"} Payload: {"sub":"123","role":"admin"} Q: Does decoding verify the JWT signature? A: No. Decoding only reads the header and payload. Verification requires the issuer key and expected algorithm. Q: Should I paste production bearer tokens? A: Avoid pasting live bearer tokens into any external page. Rotate a token if it may have been exposed. Q: Does the decoder upload my token? A: No. The decoding logic runs in the browser. ### Regex Tester With No Data Sent URL: https://inbrowser.sh/regex-tester-no-data-sent Parent tool: https://inbrowser.sh/regex-tester Summary: Test JavaScript regex patterns in your browser without uploading sample text to a server. Example input: Pattern: (\w+)@(\w+\.\w+) Text: support@inbrowser.sh Example output: Match: support@inbrowser.sh Group 1: support Group 2: inbrowser.sh Q: Which regex flavor is supported? A: The main tool uses JavaScript regular expressions. Q: Is sample text uploaded? A: No. Matching runs in the browser. Q: Can regex testing freeze a tab? A: Pathological patterns can be expensive. Keep samples small and review complex expressions carefully. ### Offline Hash Generator URL: https://inbrowser.sh/hash-generator-offline Parent tool: https://inbrowser.sh/hash-generator Summary: Generate MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes locally in your browser with no upload. Example input: abc Example output: SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad Q: Does hashing encrypt data? A: No. Hashing creates a digest. It is not reversible encryption. Q: Is the input uploaded? A: No. Hash generation runs locally in the browser. Q: Should I hash production secrets here? A: Use approved local tooling for production secrets and regulated values. ### JSON Validator With No Upload URL: https://inbrowser.sh/json-validator-no-upload Parent tool: https://inbrowser.sh/json-formatter Summary: Validate strict JSON locally in your browser. Find syntax errors without uploading API responses or config snippets. Example input: {"ok":true,"items":[1,2,]} Example output: Invalid JSON: trailing comma before ] Q: Does validation upload my JSON? A: No. The linked JSON Formatter validates in the browser. Q: Does it support comments or JSON5? A: No. It validates strict JSON, so comments and trailing commas are errors. Q: What should I use for very large JSON? A: For very large files, use a local CLI such as jq or a local editor to avoid browser slowdowns. ### Base64 Encoder With No Upload URL: https://inbrowser.sh/base64-encoder-no-upload Parent tool: https://inbrowser.sh/base64 Summary: Encode UTF-8 text to Base64 locally in your browser. No upload, no account and no server-side paste history. Example input: Hello, inbrowser.sh! Example output: SGVsbG8sIGluYnJvd3Nlci5zaCE= Q: Is Base64 encoding secure? A: No. Base64 is reversible encoding, not encryption. Q: Does encoding happen on a server? A: No. The Base64 tool runs in the browser. Q: Can it encode non-ASCII text? A: Yes. Strings are encoded as UTF-8 first. ### URL Decoder With No Upload URL: https://inbrowser.sh/url-decoder-no-upload Parent tool: https://inbrowser.sh/url-encode Summary: Decode percent-encoded URL text locally in your browser. No upload required for query strings or path segments. Example input: hello%20world%3Fq%3Dinbrowser Example output: hello world?q=inbrowser Q: Does URL decoding upload the URL? A: No. Decoding uses browser-side JavaScript. Q: What causes decode errors? A: Malformed percent escapes or invalid UTF-8 sequences can cause decoding to fail. Q: Should I decode full URLs or components? A: Decode individual components when possible so reserved characters remain clear. ### Local Unix Timestamp Converter URL: https://inbrowser.sh/local-unix-timestamp-converter Parent tool: https://inbrowser.sh/timestamp Summary: Convert Unix timestamps to dates locally in your browser. Compare seconds, milliseconds, UTC and local output. Example input: 1719792000 Example output: 2024-07-01T00:00:00.000Z Q: Does timestamp conversion need a backend? A: No. The browser can parse and format epoch values locally. Q: How do I tell seconds from milliseconds? A: Current Unix seconds are 10 digits; current Unix milliseconds are usually 13 digits. Q: Which time zone should I trust? A: Use UTC for shared logs and local time only when the user-facing context needs it. ### Local Cron Expression Explainer URL: https://inbrowser.sh/cron-expression-explainer-local Parent tool: https://inbrowser.sh/cron Summary: Explain five-field cron expressions in your browser and preview upcoming run times with an explicit time zone. Example input: 0 9 * * 1-5 Example output: Runs at 09:00 Monday through Friday. Q: Does the cron explainer support seconds? A: No. It focuses on common five-field crontab syntax. Q: Does cron use local time? A: Cron uses the scheduler or server time zone. Always verify the platform setting. Q: Is the expression uploaded? A: No. Explanation and preview run in the browser. ### HTML Escape With No Upload URL: https://inbrowser.sh/html-escape-no-upload Parent tool: https://inbrowser.sh/html-entities Summary: Escape HTML characters locally in your browser. Convert <, >, &, quotes and entities without uploading text. Example input: Hello Example output: <strong>Hello</strong> Q: Is HTML escaping the same as sanitizing? A: No. Escaping is one output-encoding step. Use a sanitizer for untrusted HTML rendering. Q: Does escaping upload my text? A: No. The HTML Entities tool runs in your browser. Q: Can I unescape entities too? A: Yes. Use the decode mode in the HTML Entities tool. ### Spring Cron Expression Generator URL: https://inbrowser.sh/spring-cron-expression-generator Parent tool: https://inbrowser.sh/cron Summary: Build and explain Spring-style cron schedules with examples, field notes and a link to the local cron parser. Example input: 0 */15 * * * * Example output: Spring: run every 15 minutes when seconds = 0. Five-field equivalent: */15 * * * * Q: Why does Spring cron have six fields? A: Spring cron expressions include seconds first, followed by minute, hour, day of month, month and day of week. Q: Can the main parser preview this exact six-field expression? A: The main parser focuses on five-field crontab syntax. Drop the leading seconds field when you need a five-field equivalent. Q: Should I use UTC for Spring jobs? A: Use an explicit zone when possible so deployments do not inherit an unexpected server time zone. ### Quartz Cron Expression Generator URL: https://inbrowser.sh/quartz-cron-expression-generator Parent tool: https://inbrowser.sh/cron Summary: Reference Quartz cron syntax with seconds, question marks, examples and five-field crontab equivalents. Example input: 0 0 9 ? * MON-FRI Example output: Quartz: run at 09:00 Monday through Friday. Five-field equivalent: 0 9 * * 1-5 Q: What does ? mean in Quartz cron? A: It means no specific value for either day-of-month or day-of-week when the other field is used. Q: Is Quartz cron the same as Linux crontab? A: No. Linux crontab typically uses five fields. Quartz normally uses six or seven fields. Q: Can I preview related five-field schedules? A: Yes. Use the main Cron Parser with the five-field equivalent shown in the example. ### AWS EventBridge Cron Generator URL: https://inbrowser.sh/aws-eventbridge-cron-generator Parent tool: https://inbrowser.sh/cron Summary: Draft AWS EventBridge cron schedules with UTC notes, examples and crontab-style comparisons. Example input: cron(0 9 ? * MON-FRI *) Example output: AWS EventBridge: run at 09:00 UTC Monday through Friday. Q: Does EventBridge cron use UTC? A: Classic EventBridge rules are UTC-based. Check EventBridge Scheduler settings if you need a named time zone. Q: Why is there a year field? A: AWS cron includes a year field as the sixth position after day-of-week. Q: Can I test a five-field equivalent? A: Use 0 9 * * 1-5 in the Cron Parser to preview the matching weekday schedule. ### Azure Functions Cron Generator URL: https://inbrowser.sh/azure-functions-cron-generator Parent tool: https://inbrowser.sh/cron Summary: Understand Azure Functions timer cron schedules with examples, UTC notes and five-field equivalents. Example input: 0 */30 * * * * Example output: Azure Functions: run every 30 minutes when seconds = 0. Five-field equivalent: */30 * * * * Q: Why does Azure timer syntax start with 0? A: The first field is seconds. Many common schedules set it to 0. Q: Is Azure Functions timer trigger local time? A: Timer triggers are often treated as UTC in cloud hosting. Verify app and platform settings before relying on local time. Q: Where can I preview the equivalent? A: Drop the leading seconds field and use the main Cron Parser for common five-field schedules. ### GitHub Actions Cron Generator URL: https://inbrowser.sh/github-actions-cron-generator Parent tool: https://inbrowser.sh/cron Summary: Build GitHub Actions schedule cron expressions with UTC examples and local preview links. Example input: 0 3 * * 1-5 Example output: Run at 03:00 UTC Monday through Friday. Q: Does GitHub Actions cron use UTC? A: Yes. Scheduled workflows are evaluated in UTC. Q: Can I use the main parser directly? A: Yes. GitHub Actions uses standard five-field cron, so paste the expression into the Cron Parser. Q: Where does the expression go? A: Use it under on.schedule with a cron value in your workflow YAML. ### Kubernetes CronJob Schedule Generator URL: https://inbrowser.sh/kubernetes-cronjob-schedule-generator Parent tool: https://inbrowser.sh/cron Summary: Create Kubernetes CronJob schedule expressions with five-field examples, UTC notes and preview links. Example input: 0 */6 * * * Example output: Run every six hours at minute 0. Q: Does Kubernetes CronJob use five fields? A: Yes. The schedule field uses standard minute, hour, day-of-month, month and day-of-week syntax. Q: Can I preview it in the main tool? A: Yes. Paste the expression into the Cron Parser. Q: Should I set a time zone? A: Use the time zone controls supported by your Kubernetes version and cluster policy when local time matters. ### UUID v7 Generator URL: https://inbrowser.sh/uuid-v7-generator Parent tool: https://inbrowser.sh/uuid-generator Summary: Generate time-ordered UUID v7 values locally in your browser. Bulk output, no upload and no signup. Example input: Format: UUID v7, count: 3 Example output: 0190f6fb-7c6b-7b88-9d84-6a1ec1f4c6a1 0190f6fb-7c6c-7b89-9f52-1cf5df7a3a91 Q: Is UUID v7 better than UUID v4? A: It depends. UUID v7 is often friendlier for database indexes because values are roughly time ordered. Q: Does generation happen locally? A: Yes. The UUID Generator runs in the browser. Q: Can I generate UUID v4 too? A: Yes. The same tool supports UUID v4, UUID v7, ULID and NanoID. ### UUID v7 Generator for Postgres URL: https://inbrowser.sh/uuid-v7-generator-postgres Parent tool: https://inbrowser.sh/uuid-generator Summary: Generate UUID v7 examples for Postgres seed data and migrations. Local browser-side output with no upload. Example input: INSERT INTO accounts (id, name) VALUES (...) Example output: INSERT INTO accounts (id, name) VALUES ('0190f6fb-7c6b-7b88-9d84-6a1ec1f4c6a1', 'Demo account'); Q: Does Postgres require a special UUID v7 type? A: No. UUID v7 values are still UUID strings and fit in the uuid type. Q: Should production IDs be generated in the browser? A: No. Use application or database-side generation for production writes. Q: Can the tool generate many values? A: Yes. The UUID Generator can produce bulk UUID v7 output locally. ### UUID v7 Generator for JavaScript URL: https://inbrowser.sh/uuid-v7-generator-javascript Parent tool: https://inbrowser.sh/uuid-generator Summary: Generate UUID v7 values for JavaScript examples and fixtures. Runs locally in your browser. Example input: import { v7 as uuidv7 } from 'uuid'; Example output: const id = '0190f6fb-7c6b-7b88-9d84-6a1ec1f4c6a1'; Q: Can browsers generate UUID v7 natively? A: Browsers expose crypto.randomUUID for v4. UUID v7 usually comes from a library. Q: Is the inbrowser.sh generator server-side? A: No. It runs in the browser. Q: Can I copy one ID per line? A: Yes. Bulk output is newline-separated for easy copying. ### ULID Generator URL: https://inbrowser.sh/ulid-generator Parent tool: https://inbrowser.sh/uuid-generator Summary: Generate sortable ULID values locally in your browser. Bulk output with no upload. Example input: Format: ULID, count: 2 Example output: 01J1X9VY7K0GB6RY4N9Y0Z4F2E 01J1X9VY7M5WH8A1TR8SKK2B8Q Q: Is ULID a UUID? A: No. It is a separate 128-bit identifier format with Crockford Base32 text encoding. Q: Does it sort by creation time? A: ULIDs sort lexicographically by timestamp prefix when generated normally. Q: Does generation upload anything? A: No. The generator runs locally. ### NanoID Generator URL: https://inbrowser.sh/nanoid-generator Parent tool: https://inbrowser.sh/uuid-generator Summary: Generate URL-safe NanoID values locally in your browser. Choose count and size with no upload. Example input: Format: NanoID, size: 12 Example output: V1StGXR8_Z5j Q: Is NanoID URL-safe? A: The default alphabet is URL-safe. Q: Can I change the length? A: Yes. The UUID Generator exposes a NanoID size field. Q: Is shorter always better? A: No. Shorter IDs have higher collision risk. Choose length based on volume and risk. ### Test Data Generator Online URL: https://inbrowser.sh/test-data-generator-online Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate online test data as JSON, CSV or SQL fixtures. Synthetic users, orders and products with no upload. Example input: Dataset: users, rows: 3, format: CSV Example output: id,full_name,email,city,status,signup_date 1,Ada Lovelace,ada.lovelace1@example.com,Austin,active,2026-01-18 Q: Is generated test data real? A: No. It is synthetic placeholder data for development and QA. Q: Does the tool upload generated rows? A: No. Generation and formatting run in your browser. Q: Which formats are supported? A: The tool exports JSON, CSV and SQL insert statements. ### Random CSV Generator URL: https://inbrowser.sh/random-csv-generator Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate random CSV fixture rows for users, orders and products locally in your browser. Example input: Dataset: orders, rows: 2, format: CSV Example output: id,order_id,customer_email,amount_usd,status,created_at 1,ORD-10001,customer1@example.com,73.42,paid,2026-02-03 Q: Can I choose JSON instead? A: Yes. The same Mock Data Generator exports JSON, CSV and SQL. Q: Does it support huge CSV files? A: No. It is intentionally capped for small QA fixtures and examples. Q: Is the data safe to share? A: It is synthetic, but still review output before publishing examples. ### SQL Insert Generator URL: https://inbrowser.sh/sql-insert-generator Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate SQL INSERT fixture statements for users, orders or products locally in your browser. Example input: Dataset: products, rows: 1, format: SQL Example output: INSERT INTO mock_products (id, sku, name, category, price_usd, active) VALUES (1, 'SKU-0001', 'Starter Plan', 'subscription', 29, TRUE); Q: Can I run the SQL directly? A: Review table names, data types and quoting before running generated SQL in any database. Q: Which SQL dialect is targeted? A: The output is simple ANSI-style INSERT statements for fixtures, not dialect-specific migrations. Q: Does SQL generation need a backend? A: No. It runs locally in the browser. ### Sample JSON Generator URL: https://inbrowser.sh/sample-json-generator Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate sample JSON arrays for users, orders and products. Local synthetic data with no upload. Example input: Dataset: users, rows: 1, format: JSON Example output: [ { "id": 1, "full_name": "Ada Lovelace", "email": "ada.lovelace1@example.com" } ] Q: Is this JSON based on a schema? A: No. This first version offers built-in user, order and product fixtures. Q: Can I convert the JSON to CSV? A: Yes. Use the related JSON to CSV tool when you need a table. Q: Does the sample JSON leave my browser? A: No. It is generated locally. ### Mock User Data Generator URL: https://inbrowser.sh/mock-user-data-generator Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate synthetic user rows with names, emails, cities, statuses and dates for QA fixtures. Example input: Dataset: users, rows: 2 Example output: full_name,email,city,status Ada Lovelace,ada.lovelace1@example.com,Austin,active Q: Are the names and emails real? A: No. They are synthetic placeholders. Q: Can I export SQL? A: Yes. Choose SQL in the Mock Data Generator. Q: Should I use this for production users? A: No. It is only for development, QA, seed data and demos. ### Mock Order Data Generator URL: https://inbrowser.sh/mock-order-data-generator Parent tool: https://inbrowser.sh/mock-data-generator Summary: Generate synthetic order rows with IDs, emails, amounts, statuses and dates for local QA. Example input: Dataset: orders, rows: 2 Example output: order_id,customer_email,amount_usd,status ORD-10001,customer1@example.com,73.42,paid Q: Are these payment records real? A: No. They are synthetic local fixtures. Q: Can I choose order status values? A: This first version uses built-in example statuses. Q: Does generation call an API? A: No. It runs in the browser. ## Conversion quick reference pages Each conversion page includes a concrete input and output example, FAQ schema and a link to the parent interactive tool. ### Base64 Encode Online URL: https://inbrowser.sh/base64-encode Parent tool: https://inbrowser.sh/base64 Input (Plain text): Hello, inbrowser.sh! Output (Base64): SGVsbG8sIGluYnJvd3Nlci5zaCE= Q: Is Base64 encryption? A: No. Base64 is reversible encoding and should not be used to hide secrets. Q: Does encoding upload my text? A: No. The Base64 tool runs in the browser. ### Base64 Decode Online URL: https://inbrowser.sh/base64-decode Parent tool: https://inbrowser.sh/base64 Input (Base64): SGVsbG8sIGluYnJvd3Nlci5zaCE= Output (Plain text): Hello, inbrowser.sh! Q: Can this decode URL-safe Base64? A: Yes. Enable the URL-safe option in the main Base64 tool. Q: Why did decoding fail? A: The input may contain invalid Base64 characters, missing padding or non-UTF-8 bytes. ### Base64 to Image URL: https://inbrowser.sh/base64-to-image Parent tool: https://inbrowser.sh/base64 Input (Base64 image data): iVBORw0KGgo... Output (Data URI): data:image/png;base64,iVBORw0KGgo... Note: Use the main Base64 tool for text. Large images are better handled with local image tools. Q: Should I Base64-encode large images? A: Usually no. Base64 increases size and can hurt caching. Use files for large images. Q: Does inbrowser.sh upload image data? A: No. Base64 conversion is browser-side. ### Image to Base64 URL: https://inbrowser.sh/image-to-base64 Parent tool: https://inbrowser.sh/base64 Input (Image file bytes): logo.png Output (Base64 data URI): data:image/png;base64,... Q: Why is Base64 image output larger? A: Base64 representation is roughly one third larger than the original bytes. Q: When should I use image to Base64? A: Use it for tiny assets or portable demos, not for normal website image delivery. ### String to Base64 URL: https://inbrowser.sh/string-to-base64 Parent tool: https://inbrowser.sh/base64 Input (String): dev tools Output (Base64): ZGV2IHRvb2xz Q: Does this support non-ASCII text? A: Yes. The Base64 tool encodes strings as UTF-8 first. Q: Can I decode the result later? A: Yes. Base64 is reversible encoding. ### Decimal to Hex Converter URL: https://inbrowser.sh/decimal-to-hex Parent tool: https://inbrowser.sh/number-base Input (Decimal): 255 Output (Hexadecimal): ff Q: Does it support large integers? A: Yes. The Number Base tool uses BigInt for integer conversion. Q: Should hex output include 0x? A: inbrowser.sh shows the raw hex digits. Add 0x if your target language or config expects it. ### Hex to Decimal Converter URL: https://inbrowser.sh/hex-to-decimal Parent tool: https://inbrowser.sh/number-base Input (Hexadecimal): ff Output (Decimal): 255 Q: Are uppercase and lowercase hex supported? A: Yes. A-F and a-f are equivalent. Q: What if my value starts with 0x? A: Remove the 0x prefix before converting in the current tool. ### Binary to Decimal Converter URL: https://inbrowser.sh/binary-to-decimal Parent tool: https://inbrowser.sh/number-base Input (Binary): 11111111 Output (Decimal): 255 Q: Can I convert negative binary values? A: The tool supports a leading minus sign for integer conversion, not two’s-complement interpretation. Q: Does it run locally? A: Yes. Number conversion runs in the browser. ### Decimal to Binary Converter URL: https://inbrowser.sh/decimal-to-binary Parent tool: https://inbrowser.sh/number-base Input (Decimal): 42 Output (Binary): 101010 Q: Does output include leading zeroes? A: No. The converter shows the shortest integer representation. Q: Can I convert very large numbers? A: Yes. The Number Base tool uses BigInt. ### Hex to Binary Converter URL: https://inbrowser.sh/hex-to-binary Parent tool: https://inbrowser.sh/number-base Input (Hexadecimal): 2a Output (Binary): 101010 Q: Why are leading zeroes missing? A: Integer conversion drops leading zeroes. Add fixed-width padding when a protocol requires it. Q: Does it support uppercase hex? A: Yes. Uppercase and lowercase hex digits are accepted. ### HEX to RGB Converter URL: https://inbrowser.sh/hex-to-rgb Parent tool: https://inbrowser.sh/color-converter Input (HEX): #6366F1 Output (RGB): rgb(99, 102, 241) Q: Does it support short HEX? A: The color parser supports common CSS color formats, including short HEX. Q: Is alpha preserved? A: Use the main Color Converter to inspect supported alpha formats. ### RGB to HEX Converter URL: https://inbrowser.sh/rgb-to-hex Parent tool: https://inbrowser.sh/color-converter Input (RGB): rgb(99, 102, 241) Output (HEX): #6366f1 Q: Are spaces required in RGB? A: No. Standard CSS rgb() forms are supported by the parser. Q: Does this upload color values? A: No. Conversion runs in the browser. ### HEX to HSL Converter URL: https://inbrowser.sh/hex-to-hsl Parent tool: https://inbrowser.sh/color-converter Input (HEX): #6366F1 Output (HSL): hsl(239, 84%, 67%) Q: Why use HSL? A: HSL can be easier for manual hue, saturation and lightness adjustments. Q: Can I preview the color? A: Yes. The main Color Converter shows a live swatch. ### RGB to HSL Converter URL: https://inbrowser.sh/rgb-to-hsl Parent tool: https://inbrowser.sh/color-converter Input (RGB): rgb(99, 102, 241) Output (HSL): hsl(239, 84%, 67%) Q: Can I convert named colors? A: Use the main Color Converter to parse common CSS named colors. Q: Does this run server-side? A: No. Color conversion runs in the browser. ### camelCase to snake_case Converter URL: https://inbrowser.sh/camelcase-to-snakecase Parent tool: https://inbrowser.sh/case-converter Input (camelCase): userDisplayName Output (snake_case): user_display_name Q: Does it handle multiple lines? A: Yes. The Case Converter processes each line. Q: What happens to acronyms? A: Consecutive uppercase letters are split using the converter’s word rules. ### snake_case to camelCase Converter URL: https://inbrowser.sh/snakecase-to-camelcase Parent tool: https://inbrowser.sh/case-converter Input (snake_case): user_display_name Output (camelCase): userDisplayName Q: Does it support spaces too? A: Yes. The converter splits common separators such as spaces, underscores and dashes. Q: Is conversion local? A: Yes. Case conversion runs in the browser. ### Text to Uppercase Converter URL: https://inbrowser.sh/text-to-uppercase Parent tool: https://inbrowser.sh/case-converter Input (Text): hello world Output (Uppercase text): HELLO WORLD Q: Does it preserve line breaks? A: Yes. The converter processes each line and preserves line breaks. Q: Does it upload text? A: No. Text conversion runs locally in the browser. ### Slugify Text Online URL: https://inbrowser.sh/slugify Parent tool: https://inbrowser.sh/case-converter Input (Text): Hello World Tools Output (Slug): hello-world-tools Q: Is slugify the same as kebab-case? A: For simple ASCII text, kebab-case is a practical slug format. Q: Should slugs be lowercase? A: Lowercase slugs are usually easier to read, share and compare. ### SHA-256 Generator URL: https://inbrowser.sh/sha256-generator Parent tool: https://inbrowser.sh/hash-generator Input (Text): abc Output (SHA-256): ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad Q: Is SHA-256 reversible? A: No. SHA-256 is a one-way hash function. Q: Does the tool upload input? A: No. Hashing runs locally in the browser. ### MD5 Generator URL: https://inbrowser.sh/md5-generator Parent tool: https://inbrowser.sh/hash-generator Input (Text): abc Output (MD5): 900150983cd24fb0d6963f7d28e17f72 Q: Should I use MD5 for security? A: No. Use SHA-256 or a modern password hashing scheme for security-sensitive work. Q: Why include MD5 at all? A: Many legacy systems still expose MD5 checksums, so it is useful for compatibility checks. ### SHA-1 Generator URL: https://inbrowser.sh/sha1-generator Parent tool: https://inbrowser.sh/hash-generator Input (Text): abc Output (SHA-1): a9993e364706816aba3e25717850c26c9cd0d89d Q: Is SHA-1 secure? A: SHA-1 is considered broken for collision resistance and should not be used for new security-sensitive work. Q: Does SHA-1 generation upload data? A: No. The digest is calculated in the browser. ### URL Encode Online URL: https://inbrowser.sh/url-encode-online Parent tool: https://inbrowser.sh/url-encode Input (Text or URL component): hello world?x=1&y=2 Output (Percent-encoded text): hello%20world%3Fx%3D1%26y%3D2 Q: Should I encode a full URL or one component? A: Encode individual query values or path segments when possible so URL separators stay meaningful. Q: Does URL encoding upload text? A: No. Encoding uses browser-side JavaScript. ### URL Decode Online URL: https://inbrowser.sh/url-decode-online Parent tool: https://inbrowser.sh/url-encode Input (Percent-encoded text): hello%20world%3Fx%3D1%26y%3D2 Output (Decoded text): hello world?x=1&y=2 Q: Why did decoding fail? A: Malformed percent escapes, such as a lone %, can make decoding fail. Q: Does this decode plus signs as spaces? A: The main tool follows URL component decoding; form-encoded plus handling depends on the source format. ### HTML Escape Online URL: https://inbrowser.sh/html-escape Parent tool: https://inbrowser.sh/html-entities Input (HTML or text): Ada & Bo Output (Escaped HTML): <span class="name">Ada & Bo</span> Q: Is escaping enough for untrusted HTML? A: No. Escaping is output encoding. Use a sanitizer when rendering untrusted HTML. Q: Does escaping happen locally? A: Yes. The HTML Entities tool runs in the browser. ### HTML Unescape Online URL: https://inbrowser.sh/html-unescape Parent tool: https://inbrowser.sh/html-entities Input (HTML entities): <strong>Hello & welcome</strong> Output (Decoded text): Hello & welcome Q: Are numeric entities supported? A: Yes. The HTML Entities tool supports named HTML5 entities and numeric references. Q: Is unescaping the same as rendering HTML? A: No. It returns text. Rendering untrusted HTML requires sanitization. ### Epoch to Date Converter URL: https://inbrowser.sh/epoch-to-date Parent tool: https://inbrowser.sh/timestamp Input (Unix timestamp): 1719792000 Output (Readable date): 2024-07-01T00:00:00.000Z Q: Is my timestamp seconds or milliseconds? A: Current seconds timestamps are 10 digits; milliseconds are usually 13 digits. Q: Does conversion upload the timestamp? A: No. Timestamp conversion runs in your browser. ### Date to Epoch Converter URL: https://inbrowser.sh/date-to-epoch Parent tool: https://inbrowser.sh/timestamp Input (Date and time): 2024-07-01T00:00:00Z Output (Unix timestamp): 1719792000 seconds / 1719792000000 milliseconds Q: Which value do JavaScript APIs use? A: JavaScript Date timestamps are milliseconds since the Unix epoch. Q: Should I use UTC? A: Use UTC when sharing timestamps across systems unless the target API says otherwise. ### Seconds to Hours Converter URL: https://inbrowser.sh/seconds-to-hours Parent tool: https://inbrowser.sh/duration-converter Input (Seconds): 7200 Output (Hours): 2 hours Q: Can I use decimal seconds? A: Yes. Decimal values are accepted in the Duration Converter. Q: Does it include months? A: No. The converter uses fixed units up to weeks and avoids variable-length months. ### Minutes to Seconds Converter URL: https://inbrowser.sh/minutes-to-seconds Parent tool: https://inbrowser.sh/duration-converter Input (Minutes): 15 Output (Seconds): 900 seconds Q: Is one minute always 60 seconds here? A: Yes. This conversion uses fixed duration units. Q: Does conversion upload my value? A: No. Duration conversion runs locally in your browser.