About PostMicroTools

What this site is

PostMicroTools is a hub of small, fast, single-purpose tools for people who work in post-production and visual effects: editors, assistant editors, colorists, DITs, VFX artists, post supervisors and producers. Bitrate and storage calculators, a timecode and frame-rate converter, a delivery-spec validator, an EXR sequence checker, a LUT previewer, a digital slate, reference pages for shutter angles, pulldown cadences, codecs and log curves — the kind of questions that come up ten times a week in a cutting room and deserve better answers than a forum thread from 2011.

Every tool follows the same design rules: it loads instantly, works on the machine you already have open, needs no account and no install, and — where it makes sense — the state is shareable by URL so you can send a colleague the exact calculation you're looking at.

Who builds it

PostMicroTools is designed, built and maintained by Furiosa Studio, an independent studio that builds focused web tools and data sites. The people behind it have spent years around real post pipelines — offline and online editorial, VFX vendor deliveries, grading sessions and the unglamorous plumbing between them: transcode farms, naming conventions, LTO archiving runs and delivery QC checklists. These tools exist because we kept rebuilding the same spreadsheets on every job, and a spreadsheet you rebuild three times is a tool that should exist once, properly.

That background shapes what the site covers. The calculators aren't generic \"video converter\" widgets; they answer working questions — will this Mac cut 6K BRAW, how many LTO-9 tapes does a 60 TB show need, does this mix pass EBU R128, why is the client's LUT crushing the blacks — with the units, presets and edge cases that professional work actually involves.

Where the numbers come from

Every constant in these tools is sourced from published, checkable references, and calibrated against them:

• Codec data rates are calibrated against manufacturer documentation — for example the Apple ProRes white paper's published rates (220 Mbps for ProRes 422 HQ at 1080p29.97, 880 Mbps at UHD) — using a bits-per-pixel model so intermediate resolutions and frame rates interpolate sensibly.
• Timecode math implements the standard SMPTE drop-frame algorithm and is verified against known fixture values, including the every-tenth-minute exception.
• Loudness targets quote the primary documents: EBU R128, ATSC A/85 and each platform's published delivery specifications.
• LUT interpolation uses the same trilinear math as grading software and is verified against an identity LUT for zero error.

When something is an estimate rather than a specification — H.264 delivery bitrates being the obvious case, since real rates depend on encoder and content — the tool says so on the page instead of pretending to precision it doesn't have.

Everything runs in your browser

This is the design decision we care most about: every tool on this site is 100% client-side. There is no upload button anywhere, no server that processes your media, no account system, no database of user data. When you drop an EXR render folder into the sequence checker, check a confidential .cube LUT against a production still, or paste a client's EDL into the inspector, all of it is parsed by JavaScript running on your machine — close the tab and it's gone.

In post-production that's not a nice-to-have. Plates, cuts and looks are routinely under NDA, and \"paste your client's unreleased film into a random website\" is not a sentence anyone should say. Because the tools are static files with no backend, there is nothing for us to receive, store, leak or get breached out of. The site uses privacy-friendly, cookieless analytics to count visits — no personal profiles, no cross-site tracking — and displays light advertising to cover its costs.

How the site is funded

PostMicroTools is free and will stay free. It costs little to run — static pages on a CDN and a domain — and it's funded by unobtrusive display ads plus a voluntary support page with small yearly contributions. Nothing is paywalled and support unlocks nothing; the tools are the same for everyone.

Corrections and contact

If a number looks wrong, it matters to us — these tools are only useful if they can be trusted. Found a data rate that disagrees with a manufacturer document, a timecode edge case that fails, or a delivery spec that a platform has since updated? Tell us via @furiosadata and we'll verify against the primary source and fix it. Requests for new tools travel the same route; several of the current tools started as exactly that kind of message.