Publisher

About FramePad

Last updated 28 August 2026 · framepad.app

FramePad is an independent web application for checking vertical-video safe zones and converting 16:9 footage to 9:16 in the browser. It exists because social apps cover a surprising amount of a 1080×1920 frame with captions, tabs, and buttons, and because most “online converters” require you to upload the file to someone else’s server to find that out.

Who publishes this site

FramePad is published by an independent editorial desk that also builds the studio. We are not affiliated with TikTok, Instagram, Meta, YouTube, Snapchat, or X. Overlays are reconstructions for measurement. Contact: hello@framepad.app. The legal entity notice, terms, and privacy policy live at /terms and /privacy.

What we measure

Every overlay starts as a 1080×1920 design. We photograph the live player on iPhone 15 Pro Max, iPhone 16 Pro Max, and Samsung Galaxy S24 Ultra, then align chrome to percentages that survive small panel differences. A collision is recorded when burned-in type or a face intersects a live control by more than eight pixels at native 1080×1920. When a platform ships a chrome change, we re-shoot and publish a note in the revision log on the contact page.

We do not claim pixel-perfect identity with every account, A/B test, or accessibility font size. We claim a conservative map that was true on those three devices on the shoot date. Confirm a final cut on the destination phone before you spend media budget. That sentence is also in the terms because it is the honest limit of a reconstruction.

Why processing stays in the tab

Unreleased product, unpaid talent, and draft campaigns should not be posted to a transcode queue to check a like button. FramePad reads files through object URLs, draws them in Canvas 2D, and exports a blob. The client-side privacy guide explains what that means in a network panel, and what third-party scripts (fonts, optional WASM, analytics) do run.

Editorial desk

Guides on this site are written by the same people who update the overlays. We do not syndicate other sites’ spec sheets. We do not sell placements in the articles. Corrections go to hello@framepad.app; the editorial policy describes how we handle them. The guide library is the long-form companion to the studio, not a doorway of keyword pages.

What FramePad is not

It is not a cloud renderer, a multi-track NLE, or an official partner tool. It will not replace a hardware encoder for a two-hour master. It will show you, in this tab, whether a 9:16 cut is about to lose a face to a caption well.

How to use this site as a publisher

The studio is the product. The guides are the long-form record of why the overlays look the way they do. The methodology page is the protocol (devices, eight-pixel collision rule, 1080×1920 alignment). The glossary is the vocabulary. The changelog is when chrome moved. Read those even if you never drop a file. They are original to this desk; they are not scraped spec sheets.

If you find an error, we want the correction more than we want the traffic. Email hello@framepad.app with the phone, OS, and app version. Do not attach unreleased media unless you intend to. We cannot receive a file through the studio, and we will not ask you to upload one.