Sharpening increases perceived edge contrast. It can make slightly soft photos look clearer, but it cannot recover detail that was never captured and can exaggerate noise or halos.
or drag and drop images here
Fast async jobs
No install required
Temporary files
Batch uploads
.png, .jpg, .jpeg, .webp
same_as_input, jpg, png, webp
/filter
Submit files to /filter, poll the job endpoint, then download outputs programmatically.
Sharpening increases perceived edge contrast. It can make slightly soft photos look clearer, but it cannot recover detail that was never captured and can exaggerate noise or halos.
Sharpening usually estimates high-frequency detail by comparing the image with a blurred version, then adds a controlled contrast boost around edges.
Moderate cost. It is usually fast enough for web-sized images, but high-radius sharpening on large files can become expensive.
Controls how strongly edge contrast is boosted.
Controls how wide the edge effect spreads.
Removes metadata from generated output when supported.
Only a little. Sharpening improves perceived crispness but cannot recreate detail that was never captured.
Noise is high-frequency detail too, so sharpeners often boost it unless denoise is applied first.
Only slightly. Sharpening can improve edge perception but cannot truly restore out-of-focus or motion-blurred detail.
Strong edge contrast can create bright/dark outlines around edges, especially at high radius or amount settings.
Usually sharpen after final resizing because resizing changes edge detail.
Yes, it can make noise and compression artifacts more visible.
Yes. Upload an image, apply the filter through ImageHQ, and download the processed result from the browser.
No. Filter pages are frontend SEO routes that submit to the compact POST /v1/filter API.
MDN Web Docs - browser_documentation
ImageMagick - library_documentation
W3C WAI - standards_body
libvips - library_documentation