Round the corners of any image - download as PNG or JPG.

For photographs, 8 to 24 pixels is the sweet spot. Below 8px the rounding is barely visible on most screens; above 24px it starts to look like a deliberate design decision rather than a subtle refinement. Portfolio images and blog post thumbnails typically work best at 12 to 16px, which matches the rounding you see in Apple Photos, Google Drive previews, and most modern card-based layouts. For UI mockups and app screenshots, bump up to 20 to 40px to match iOS and Android component defaults. Social media profile frames are a different case - platforms like Facebook and LinkedIn display profile photos with heavy rounding (around 48% of the image width), so a 90px or "Pill" preset gets you closest to that look before you crop. For a full-circle result, use the Circle Crop tool instead, which is designed specifically for that shape rather than approximating it with a very large border radius.

Rounding corners creates transparent pixels in the four corner areas - the original rectangle gets clipped and those cut-away regions become empty (alpha = 0). JPEG does not support transparency. If this tool forced a JPEG output, those transparent corner pixels would be filled with a background color - typically white or black depending on the implementation - which would look like hard square corners of a different color rather than true rounded edges. PNG supports full alpha transparency per pixel, so the corners are genuinely empty and the rounded image will sit cleanly on any background color you place it on in CSS, Keynote, PowerPoint, or image editors. The tradeoff is file size: a JPEG original converted to a rounded PNG will be larger than the original, because PNG is lossless and stores color data for every pixel. For web use, consider converting the output PNG to WebP afterward using the WebP to JPG tool in reverse - most modern browsers support transparent WebP, which cuts file size by roughly 25 to 35% versus PNG.

The direction of the file size change depends on the original format. PNG originals stay roughly the same size or get slightly smaller after rounding because the transparent corner regions compress very efficiently - a block of zeroed-out alpha values is nearly free in PNG compression. A 1200x800 PNG that is 180KB might become 170KB rounded, because lossless compression squeezes out the zero-alpha corner blocks easily. JPEG originals converted to rounded PNG are a different story: JPEG files are typically 4 to 8 times smaller than an equivalent PNG because JPEG uses lossy compression. A 150KB JPEG becoming a rounded PNG can easily reach 600KB to 900KB. For web deployment, the practical path is to apply the rounding here, then run the PNG through a compression tool like TinyPNG (which applies lossy PNG compression) to recover most of that file size. A well-compressed rounded PNG for a standard blog thumbnail (800x500px) typically lands between 60KB and 120KB after compression.

This tool clips the image to rounded corners and outputs a clean transparent-background PNG. Adding shadows or borders is a separate step best done with CSS or a design application. In CSS, apply box-shadow on the img tag: `img { border-radius: 16px; box-shadow: 0 4px 16px rgba(0,0,0,0.15); }`. For print or presentation use where CSS is not available, open the downloaded PNG in Canva, Figma, or Keynote and add a drop shadow through the layer effects panel - most offer shadow controls with offset, blur, and color. A subtle shadow (x: 0, y: 4, blur: 12, opacity: 20%) works for most light backgrounds. For a visible border, wrap the image in a div with `border: 2px solid #e5e7eb; border-radius: 16px; overflow: hidden;` rather than baking the border into the PNG - that way you can change the border color without re-exporting the image.

iOS app icons use a "squircle" shape - not a true rounded rectangle but a superellipse that Apple renders at approximately 27% of the icon dimension. For a 1024x1024 app icon, that is roughly 277px. On device, a 180x180px icon gets about 48px rounding. For App Store screenshots, Apple does not enforce rounded corners on the images themselves; the store renders them with roughly 12px rounding in its display frame. Android adaptive icons use a 108dp safe zone and a system-controlled mask shape. For general UI card components, Google Material Design 3 specifies 12dp (medium) as the default for most surfaces, while iOS Human Interface Guidelines use 10pt for standard list cells. Twitter and X render profile photos as perfect circles. LinkedIn uses rounded rectangles at about 6px for company logos in cards. Facebook event covers and page headers are displayed with sharp corners on most surfaces.

Yes. When you upload a PNG that already has a transparent background - a product cutout, a logo, a sticker - the tool clips only the shape content, not the entire bounding rectangle. Existing transparency in the image is preserved throughout the clipping operation. The canvas draws the original PNG (keeping all its transparency intact) and then applies the rounded clip path, which only affects the rectangular outer boundary of the image frame. So if your logo is a circle already sitting inside a 400x400 transparent square, rounding the corners of that square with a small radius like 16px does very little visible work - the circle content is well inside the clip boundary. Where this matters most is cutout product images for e-commerce - a shoe photographed on white background becomes a cutout with transparent white removed, and adding a subtle 12px rounding gives those product cards a more polished appearance in grid layouts without any visible white-corner artifacts.

No. The rounding process runs entirely in your browser using the HTML5 Canvas API. Your image loads from your local device into browser memory, the clip path runs on your CPU, and the resulting PNG downloads directly to your file system. Open browser developer tools (F12) and check the Network tab while rounding an image - you will see zero outgoing image data requests. The only network activity is the initial page load of roughly 165KB of JavaScript. After that, the tool works fully offline. Closing the browser tab immediately clears all image data from memory. No cookies track your uploads, no server logs record your file names, and no third-party analytics receive your image content. This makes the tool suitable for confidential client work, internal design assets, proprietary product photography, and personal family photos that you would prefer not to pass through a third-party image processing service.