Developer tools
Small utilities, clear output.
Focused browser tools for common data and CSS tasks. No uploads, accounts, or third-party processing.
JWT Expiry Calculator
See if a token has expired, time left and lifetime; convert exp, iat and nbf.
ReferenceMIME Type & Extension Mapper
Map common extensions to MIME types and reverse-lookup extensions.
ReferenceHTTP Status Codes Lookup
Search every registered code: meaning, caching, retry and typical fix.
Referencechmod Calculator
Octal, symbolic and checkbox permissions with the chmod command.
URL dataQuery-string Parser & Builder
Edit key/value rows without losing duplicate keys or order.
Data formatJSON Lines / NDJSON Validator
Find malformed records by line and convert arrays to or from JSON Lines.
JSONJSON Escape / Unescape
Escape text into a JSON string literal and reverse it with error position.
JSONJSONPath Tester
Run RFC 9535 queries and see every match with its normalized path.
CSSCSS Clamp Calculator
Build responsive clamp values in px or rem with a live preview.
PostgresPostgres Table Size Calculator
Row size, rows per page and heap size from your column types.
PostgresB-tree Index Size and Depth Calculator
Tree depth, entries per page and index size from row count and key width.
AWSDynamoDB Capacity Calculator
RCU and WCU from item size and rate, with on-demand against provisioned cost.
RedisRedis Memory Calculator
Maxmemory and RAM budget from a measured bytes-per-key figure.
ConnectionsConnection Pool Size Calculator
Pool size from cores and spindles, split across app instances.
KafkaKafka Partition Calculator
Partitions from throughput, plus replicated retention storage.
Data structuresBloom Filter Calculator
Bits, hash count and false positive rate for n items.
KeysUUID vs Bigint Key Overhead Calculator
Extra storage from UUID keys across the table, foreign keys and indexes.
CachingCache Hit Ratio Savings Calculator
Backend load and latency at a given cache hit ratio.
OperationsBackup Window and Replication Lag Calculator
Backup duration and replica catch-up time from measured rates.
ReliabilityUptime SLA Calculator
Allowed downtime per day, month and year for any uptime SLA.
ReliabilityUptime Percentage Calculator
Availability and nines from minutes of downtime, with an SLA check.
ReliabilityError Budget Calculator
SLO to allowed downtime minutes and failed requests.
ReliabilitySLO Burn Rate Calculator
Burn rate and days until the error budget runs out.
ReliabilityMulti-Window Burn Rate Alert Calculator for SLO Alerting
Burn rate alert thresholds from the Google SRE Workbook.
ReliabilityComposite SLA Calculator
Combined availability of chained or redundant services.
ReliabilityMTBF MTTR Availability Calculator
Availability from MTBF and MTTR, and the MTTR a target allows.
ReliabilityDowntime Cost Calculator
Yearly downtime exposure from your own hourly cost.
What is in the developer utilities collection
The cards above are small, single-purpose tools for jobs that come up when you build or run a web service. They fall into five groups: reading and converting data, looking up standards, building CSS values, sizing infrastructure, and reliability and uptime. Everything runs in your browser. You paste or type, and nothing is uploaded or saved to an account.
Data and format tools
The JSON escape and unescape tool turns text into a JSON string literal and back. JSON requires the quotation mark, the backslash and control characters below U+0020 to be escaped inside a string, which is why pasting a multi-line message into a config file breaks it. The JSONPath tester runs queries written to the RFC 9535 standard and shows each match with its normalized path. The JSON Lines validator checks files where each line is one JSON value, the format used for logs and bulk exports; a blank line is not valid, and the file is UTF-8 without a byte order mark. The query-string parser and builder keeps duplicate keys and their order, because a URL such as ?tag=a&tag=b is a list of pairs rather than a map.
Reference lookups
The HTTP status code lookup explains codes by class: 1xx informational, 2xx successful, 3xx redirection, 4xx client error and 5xx server error, as defined in RFC 9110. The MIME type mapper converts file extensions to media types and back, using the common types registered with IANA. The chmod calculator converts between octal, symbolic and checkbox permissions. In octal each digit is a sum of read (4), write (2) and execute (1), written in the order owner, group, other, so 640 means owner read and write, group read, and nothing for others. The JWT expiry calculator reads the exp, iat and nbf claims. These are NumericDate values: seconds since 1970-01-01 UTC, not milliseconds. JavaScript’s Date.now() returns milliseconds, so a mix-up makes a token look like it expires tens of thousands of years from now. RFC 7519 also lets servers allow a small clock-skew leeway, usually no more than a few minutes.
CSS
The CSS clamp calculator builds clamp(min, preferred, max) values in pixels or rem, so a font size or spacing value grows with the viewport between two limits. The preview lets you check both ends before copying the value.
Sizing calculators
The remaining tools estimate capacity from numbers you supply: the Postgres table size and B-tree index size and depth calculators, DynamoDB capacity, Redis memory, connection pool size, Kafka partitions, the Bloom filter calculator, UUID versus bigint key overhead, cache hit ratio savings, and backup window and replication lag. They are planning tools. Postgres, for example, stores tables in pages of 8 kB by default, with a 24-byte page header and a 4-byte item pointer per row, which is why a row-size estimate does not translate directly into table size. Treat the output as a starting point and replace it with measurement once you have data.
Reliability and uptime calculators
The reliability group turns a target into minutes you can plan around: the uptime SLA calculator, uptime percentage calculator, error budget calculator, SLO burn rate calculator, multi-window burn rate alert calculator, composite SLA calculator, MTBF and MTTR availability calculator and downtime cost calculator. The arithmetic is simple, and worth checking by hand once. A 99.9% target leaves 0.1% of a 30-day month (43,200 minutes) as allowed downtime, which is 43.2 minutes; 99.99% leaves 4.32 minutes. Two services in a chain that are each 99.9% available give 0.999 × 0.999 = 99.8001% together, because both must be up. Two independent copies of a 99% service in parallel fail together only 1% × 1% of the time, so availability is 99.99%. Availability from repair data is MTBF divided by MTBF plus MTTR. Burn rate is how fast, relative to the SLO, a service is consuming its error budget. A rate of 1 uses the budget exactly over the SLO window. In the Google SRE Workbook’s example for a 99.9% SLO, a burn rate of 14.4 sustained for one hour (with a 5-minute short window) consumes 2% of the budget and pages someone, while a burn rate of 1 over three days consumes 10% and opens a ticket.
Measure after you estimate
- Postgres:
pg_total_relation_sizereturns the size of a table including its indexes and TOAST data;pg_indexes_sizereturns the indexes alone. - Redis:
MEMORY USAGE keyreports the bytes a key and its value need in RAM, including administrative overhead, and it samples nested values, so the figure for a large collection is an estimate. A measured bytes-per-key number is what the Redis memory calculator expects. - Other tools: use the load numbers from your own monitoring for throughput, hit ratio and replication lag rather than a guess.
How to choose a tool
If a request fails and you do not know why, start with the status code lookup. If a token is rejected, check its expiry claims. If a config file will not parse, validate or escape the string. If a query is slow or a database is growing faster than planned, use the sizing calculators with real row counts and key widths. When none fits, the full Developer Tools index lists formatters, validators, generators and converters.
Sources
Each source below was opened and checked in October 2026 (retrieved 2026-10).
- Google SRE Workbook, Alerting on SLOs: burn rate definition and the 14.4, 6 and 1 burn-rate alert table for a 99.9% SLO
- RFC 7519, JSON Web Token (JWT): exp, nbf and iat claims, NumericDate in seconds, clock-skew leeway
- RFC 9110, HTTP Semantics: status code classes
- RFC 9535, JSONPath: query syntax and normalized paths
- RFC 8259, The JSON Data Interchange Format: string escaping rules
- JSON Lines: one JSON value per line, UTF-8, blank lines not valid
- The Open Group, chmod (POSIX): octal permission bits
- WHATWG, URL Standard: query strings parse to a list of name-value pairs, keeping duplicates
- IANA, Media Types: registry of media types
- MDN, Date.now(): returns milliseconds since the epoch
- MDN, clamp(): min, preferred and max values
- PostgreSQL documentation, Database Page Layout: 8 kB pages, 24-byte header, 4-byte item pointers
- PostgreSQL documentation, Database Object Size Functions: pg_relation_size, pg_indexes_size, pg_total_relation_size
- Redis, MEMORY USAGE: bytes for a key and value including overhead, sampling for nested types
Frequently asked questions
Are these developer utilities free?
Yes. There is no account or paywall, and every tool runs in your browser, so the text and numbers you enter are not sent to a server.
Why does my JWT look expired in the wrong year?
JWT time claims such as exp, iat and nbf are in seconds since 1970-01-01 UTC. JavaScript's Date.now() returns milliseconds. If you store a millisecond value in a claim, readers interpret it as a date tens of thousands of years away.
What does chmod 755 mean?
Each digit is the sum of read (4), write (2) and execute (1), in the order owner, group, other. 755 gives the owner read, write and execute (7), and the group and others read and execute (5). The chmod calculator shows the same permissions as symbols and checkboxes.
What is the difference between JSON and JSON Lines?
JSON is one value, usually a large array or object. JSON Lines is a text format where every line is its own valid JSON value, so a file can be streamed and appended to line by line. Blank lines are not allowed.
How accurate are the database and cache sizing calculators?
They calculate from the figures you enter, so they are as good as those inputs. Real sizes depend on data distribution, encoding and overhead. Compare the estimate with a measurement such as pg_total_relation_size in Postgres or MEMORY USAGE in Redis, then update the inputs.
Which standard does the JSONPath tester follow?
RFC 9535, the standardised JSONPath specification. Each result is shown with its normalized path, which is the canonical way to address that exact value.
How much downtime does 99.9% availability allow?
0.1% of the period. Over a 30-day month that is 43.2 minutes, and over a 365-day year it is 525.6 minutes, about 8.76 hours. The uptime SLA calculator gives the figure per day, month and year for any percentage.
Is any data stored or sent anywhere?
No. The utilities process what you enter inside the page. There is no upload step and nothing is saved to an account.