Why a raw screenshot looks wrong
A screenshot is a rectangle of pixels cut out of a much larger screen. On its own it has no edges, no context and no breathing room, which is why one pasted into a slide or a blog post always looks like it fell there by accident.
Three things fix that, and none of them require design skill. Padding gives the image somewhere to sit instead of butting against the text around it. Rounded corners and a shadow tell the eye this is a window, not a stain on the page. And a background puts the whole thing on purpose, which is why every product launch post you have ever seen uses one.
What this tool does that a screenshot editor does not
Most tools make you do these one at a time: crop somewhere, add a border somewhere else, then find a gradient generator. That is three tools and two exports, and the exports are where quality goes to die.
Here it is one pass. Set the padding, the corners, the shadow, the frame and the background, see the result immediately, and export once. The only compression that touches your image is the final PNG, which is lossless.
The window frame, and when to leave it off
The frame draws a fake title bar with the three traffic light dots above your image. It is a convention, not a lie: it signals that what you are looking at came from an application window.
Use it when the screenshot is of an app or a website and the context helps. Leave it off when the screenshot is of a phone, of a terminal, or when it is a crop of something small, because a title bar over a fragment reads as clutter.
What size to export, depending on where it goes
The output shape setting exists because every place you post a screenshot crops it differently, and the crop is decided by the platform, not by you.
| Where | Shape | Why |
|---|---|---|
| X, LinkedIn, a blog post | 16:9 | Fills the preview card without the top and bottom being cut |
| Instagram feed | 1:1 | The square is the only shape that never gets cropped |
| Stories, Reels, TikTok | 9:16 | Anything else gets pillarboxed with grey bars |
| Documentation, a ticket, a slide | Fit the image | No wasted space, and the reader is already looking at it deliberately |
The rule underneath: pick the shape of the container, not the shape of your screenshot. A tall screenshot in a 16:9 frame gets padding on the sides, which looks intentional. A tall screenshot posted raw gets cropped by the platform, which does not.
Blank out anything private before you export
Screenshots are the most sensitive images most people share. Account numbers, message threads, email addresses, an open tab you forgot about in the corner. Once it is a PNG in someone else's chat, it is out of your hands.
Two habits worth having. Crop first, then beautify. The fastest way to remove something is to not include it, and a tighter crop is usually a better screenshot anyway. Check the edges. The thing that leaks is almost never the subject; it is the notification that slid in at the top, or the bookmark bar, or the file path in the title.
If you do need to hide something inside the image, cover it with a solid block rather than blurring it. Blur and pixelation can sometimes be reversed on short predictable text like a number. A solid rectangle cannot.
Why the export is a PNG
Screenshots are the worst case for JPEG. JPEG throws away fine detail, and the edge of a letter is nothing but fine detail, so text picks up a grey halo that gets worse every time the file is re-saved.
PNG is lossless. The file is larger, sometimes several times larger, and that is the trade being made on purpose. A screenshot exists to be read, and a smaller file that is harder to read has not saved you anything.
If the size genuinely matters, reduce the padding or pick a solid background instead of a gradient. Both cut the file substantially, because flat colour compresses far better than a smooth blend.
Nothing is uploaded, and you can check
The image is read by this page and drawn onto a canvas element. There is no upload, no queue and no server that briefly holds your file. If you want to confirm it, load this page, disconnect from the network, and edit an image anyway. It works, because there was never a request to make.
That matters more with screenshots than with most images. Screenshots are how people capture bank apps, message threads, boarding passes and half-finished work, and those are exactly the files you should not be handing to a stranger's server to add a gradient.