About PixelSpec

What this is

PixelSpec answers one question well: what size should this image be? For every platform and asset we list the exact pixels, the aspect ratio, the safe zone and the file limits, then put a resizer right there so you can act on the answer. There are 51 specs across 18 platforms and counting.

Why we built it

Search for any image size and the top results are design tools that bury the number under marketing and a call to open their editor. That is a slow way to learn a simple fact. We wanted the answer first, an honest date next to it, and a tool that respects your privacy. No account, no upload, no editor push.

How it stays accurate

Platforms change their recommended sizes from time to time. Every spec carries a last-verified date, and when something changes we update the data and refresh that date rather than leaving a stale screenshot online. The sitewide sweep was last run on July 2, 2026, and individual specs carry newer dates where they have been re-checked since. The changelog records every correction with the date it happened, including the ones where we were the thing that was wrong.

Documented sizes versus conventions

Plenty of the sizes people search for are not published by anybody. Telegram documents 512 by 512 for stickers, not for channel photos. TikTok documents a 20 by 20 minimum for an advertiser profile image and nothing at all for a personal avatar. A reference that quietly presents those as platform requirements is making things up, however good the number is.

So every spec here is labelled. Documented means the platform publishes that number itself and the page links to where it was read from. Convention means it does not, and the number is the one the industry has standardised on. Both are useful answers. Only one of them is a fact about the platform, and you should be able to tell which you are getting.

Privacy

Every tool runs in your browser. Your images are processed on your device with the canvas API and are never uploaded. See the privacy policy for the details.

Who maintains this

PixelSpec is built and maintained by FusionStudios, a Dutch web studio run by Jamey Weber. This one exists because the studio kept needing these numbers, kept finding guides that would not say when they were last checked, and decided it was less work to maintain a reference than to keep re-checking other people's.

Corrections are checked against the platform's own documentation where it exists, and recorded in the changelog with the date, including the ones where the thing that was wrong was this site.

Methodology

A size labelled documented was read from a page the platform publishes itself, and that page is linked on the spec. A size labelled convention is a figure the industry settled on for a surface the platform documents nothing about. The default for an unlabelled entry is convention, never documented: an unverified spec makes the weaker claim, never the stronger one.

Where a platform publishes a number but only behind documentation that renders in the browser, so there is no page that can be opened and read, the spec says so in plain words rather than showing a badge implying a link that does not exist. A plausible URL nobody opened would be worse than an admitted gap.

Each spec carries its own verification date, which moves only when a person re-checks that individual number. It is never set from the build date. A build-stamped verification date would make the freshest-looking reference on the internet out of a site nobody had checked, and that is fraud against the reader rather than a shortcut. When a platform changes something without announcing it, which is the normal case, it surfaces at the next check and the correction is dated in the changelog.

Get in touch

Spotted a size that has changed, or a platform we are missing? Tell us on the contact page. Corrections are the most useful thing you can send.