To apply the blur effect in InShot, import a photo or video, tap the clip on the timeline, open the Effects or Filters panel, and choose one of the built-in blur presets, but the result is a full-frame effect, not a pixel-coordinate selection. InShot's mobile workflow is convenient for quick social edits and works entirely on a phone, yet it does not let you target a specific rectangle by exact pixel coordinates, and the export is whatever resolution the app's encoder produces from its internal canvas. For users who need a pixel-precise, fully local, full-resolution blur that runs in any modern browser, the Blur Image tool at /image/blur-image/ handles the same job on JPG, PNG, and WebP files without uploading anything to a remote server. This guide walks through both paths so you can decide whether InShot's mobile speed or the browser's precision better matches the image you need to soften, and explains how to use Blur Image step by step when pixel control, edge clamping, or a clean full-resolution PNG export is what you actually need from the result.
What the Blur Effect in InShot Does
To apply the blur effect in InShot, open the app, start a new project, import a photo or video clip, tap the clip on the timeline, and choose a blur preset from the Effects or Filters panel. The preset softens the entire frame as a one-tap visual filter, and you can adjust how long the effect lasts by trimming its position on the timeline. The blurred result is then exported at the resolution InShot's encoder produces.
The blur in InShot is designed for speed on a phone. It does not expose pixel-coordinate selection for a specific region, there is no user-facing radius slider, and there is no documented separation between a smaller preview and the export canvas. For most social clips those limitations are acceptable. For tasks like softening a single background block on a still photo, targeting a license plate by exact rectangle, or producing a PNG at the source image's original pixel dimensions, the in-app blur either cannot do the job or requires workarounds such as layering, masking, or exporting to another editor.
This is the gap that a browser-based blur tool fills. If you searched for how to use blur effect in InShot because you want a precise rectangle on a still photo, or because you need a clean PNG export at the original pixel size, the steps below for Blur Image cover the alternative path.
Where InShot's Blur Stops Being Enough
Three situations push users off InShot's built-in blur toward a more controlled workflow:
- Pixel-coordinate control. You know the exact rectangle you want to soften, such as a meter readout at X=420, Y=180, width 240, height 80, and you want that selection to be repeatable across re-renders.
- Full-resolution export. You need a PNG whose pixel dimensions match the source image, not a downscaled social-ready version that the phone editor optimizes for sharing.
- Files that should not leave the device. You are working with a draft screenshot, an internal presentation asset, or a document scan that you do not want to push through a phone-app cloud queue, even briefly.
None of these are blockers for a phone editor in principle, but they are the specific reasons people search for an alternative after trying the in-app blur. A browser tool that decodes the image locally, draws it on a canvas, applies a radius-driven blur, and exports a PNG addresses all three at once. The rest of this article focuses on that path.
A Local Browser Alternative: Blur Image
Blur Image is a focused single-page tool that runs entirely in the current browser tab. The image is decoded, drawn, blurred, and exported without any network round-trip, so there is no upload step, no server-side copy, no account, and no retention. That makes it suitable for ordinary photos, presentation assets, screenshots, draft graphics, and backgrounds that should not leave the computer merely to receive a visual effect.
The tool supports JPEG, PNG, and WebP inputs up to 25 MB on file size and 40 megapixels on decoded dimensions. The decoded-pixel budget exists because compressed file size alone does not reveal how much memory a browser needs for a canvas; a small WebP can decompress to a very large bitmap, and the cap prevents the page from locking up on extreme inputs. Files outside those limits are rejected with a specific message before any blur is generated.
Two modes are available: a full-image blur for an evenly softened picture, and a rectangle blur that targets one specific region. In both modes the export is rendered on a separate offscreen canvas at the source image's natural pixel width and height, then written out as a PNG. The on-page preview is scaled down for inspection only and never becomes the download. For readers who want to compare how the same blur behaves across file formats, the JPG, PNG, and WebP blur guide walks through that comparison in more detail.
How to Use Blur Image Step by Step
- Choose a JPG, PNG, or WebP image. Pick the file from your computer. After it loads, the page displays the image's pixel dimensions so you can plan a rectangle if you need one.
- Pick the mode. Select full-image blur if you want a uniform softening across the picture, or switch to rectangle mode if you only want a specific area blurred.
- Enter rectangle coordinates in rectangle mode. Type the X and Y values plus the width and height, all in original-image pixels. The tool clamps any rectangle that extends beyond an edge to the available image area, so a coordinate that overshoots will not fail or expand the output canvas.
- Set the blur radius. Move the radius slider from a light softening to a much stronger blur. There is no fixed "right" value; it depends on the image size and how soft you want the result.
- Generate the preview. Click the action button, then inspect the on-page preview. The visible preview may be smaller than the source, which is normal and only affects inspection, not the export.
- Check the reported output dimensions. Before downloading, the page reports the export's pixel width and height. These should match the source image's natural dimensions, not the preview size.
- Download the PNG. Save the file and open it at 100 percent zoom. Verify the selection boundary, the output size, and any text or faces that motivated the edit. If the area is off, update the pixel coordinates and generate again, because each new generation replaces the previous browser download object.
Full-Image Blur vs Rectangle Blur
The two modes serve different jobs, and the right choice depends on what you are trying to soften.
| Aspect | Full-image mode | Rectangle mode |
|---|---|---|
| Area covered | Every pixel of the source | Only the clamped rectangle; the rest stays as the original |
| Typical use | Softening a busy background, hiding full-image detail, mockup backgrounds | Targeting a face, plate, document field, watermark, or other local region |
| Inputs required | Blur radius only | X, Y, width, and height in original pixels plus radius |
| Edge behavior | Not applicable | Coordinates are clamped to the image; overshoots do not expand the canvas |
| Edge softness | Uniform across the whole frame | Hard selection edge; blur kernels can blend nearby colors into the rectangle, which is normal blur behavior |
| Inspection tip | Check overall mood and any text that becomes unreadable | Open the downloaded PNG at 100 percent and verify the boundary and any nearby text or faces |
For a uniform softening of a background, full-image mode is usually simpler and faster. For privacy edits, document redaction previews, or hiding one element in a presentation slide, rectangle mode is the right choice, but it requires you to know or estimate the pixel coordinates of the region you want to soften.
File Limits and How Edge Coordinates Behave
The limits below determine whether a given image can be processed at all, and they interact with each other.
| Constraint | Limit | What happens at the limit |
|---|---|---|
| Accepted input formats | JPEG, PNG, WebP | Other formats are rejected before processing |
| Maximum file size | 25 MB | Files above 25 MB are rejected with a specific message |
| Maximum decoded dimensions | 40 megapixels | Images whose decoded pixel count exceeds this are rejected with a specific message |
| Output format | PNG | Always exported as PNG from a separate full-resolution canvas |
| Rectangle overshoot | Clamped to available image area | The output canvas is not expanded; the blur simply stops at the actual edge |
These limits interact: a 24 MB file can still be rejected if it decodes to more than 40 megapixels, and a small file can be rejected only if it is in a non-supported format. When the page reports a rejection, the message identifies which limit was hit, so you can decide whether to compress the file, resize it, or convert its format before retrying.
Privacy, Redaction, and What Blur Cannot Guarantee
A blur is a visual effect, not secure redaction. A blurred face, address, account number, license plate, document field, or private message can remain recognizable, recoverable from the original file, or inferable from surrounding context. If the goal is to publish an image safely, the source pixels themselves should be removed or covered with a workflow designed for redaction, and the exported file, its metadata, any hidden layers, and the surrounding text should be reviewed before publication.
For casual design needs, such as softening a busy background, blurring a watermark on a draft mockup, or hiding a face in a thumbnail where the original is already public, the visual blur in Blur Image is enough. For anything that has to be irreversibly removed, treat the blur as a preview, not a guarantee. The tool deliberately avoids automatic face detection, cloud analysis, or claims about what the image contains; you decide what to blur, and the browser performs only that requested pixel operation.
A reliable workflow is to keep the original file, upload a working copy, choose the area and radius, generate the PNG, and open the download at 100 percent zoom. Check the selection boundary, the output dimensions, and any text or faces that motivated the edit. If anything is wrong, update the pixel coordinates and generate again. Each new generation replaces the previous browser download object, while changing files or leaving the page releases the temporary object URLs.