iformat

Who builds and reviews iFormat

One person builds and maintains this site, and that person's name is on every page. Below is who that is, what gets checked before a page goes live, and what to do when something here is wrong.

Pavan Polineni

Founder & Lead Developer

polinenipavan

Full-stack developer who built iFormat.io from scratch as a solo project. Writes the file conversion and compression engines, and personally reviews every tool page for technical accuracy against W3C, ISO, and IETF specifications. Handles everything from the Django backend to the Cloudflare CDN configuration.

Expertise

  • File format standards (W3C, ISO/IEC)
  • Image and video codecs
  • Django & Python

What happens before a page goes live

Four checks, in this order. They exist because getting any of them wrong is how a file tool quietly wastes someone's afternoon.

  1. 01

    The claim is checked against the specification

    Format behaviour is taken from the standard, not from other websites: W3C for image formats, ISO/IEC for JPEG and PDF, and IETF RFCs for container and transport details.

  2. 02

    The engine is made to prove it

    An automated suite generates a real file for each supported format, pushes it through the production conversion and compression code, and reports any pair that fails. A page does not claim a conversion the engine cannot perform.

  3. 03

    Limits are read - not typed

    File-size ceilings, batch sizes and daily limits shown on a page come from the plan records the application actually enforces. When a limit changes, the page changes with it rather than drifting out of date.

  4. 04

    The wording is written - not generated

    Format pages are written per format. An automated check measures how much of each page's wording is unique across the site and flags anything that reads as a template with the format name swapped in.

Found something wrong?

Specifications change, codecs get deprecated, and limits move. If a page here states something inaccurate, tell me and I will correct the page rather than quietly leave it. Corrections are made to the source the page reads from, so the same mistake cannot survive somewhere else on the site.

Report an inaccuracy
Reviewed against
W3C · ISO · IETF
Maintained by
One person