Remove Metadata From a PDF (Author, Title, Dates)
Every PDF carries the author, title and software that made it. Learn what it knows about you, how to check it, and how to strip it before you send.
Read the guide →Tested step-by-step answers to the problems that actually stop people: form photos that get rejected, location data hiding in uploads, PDFs that won't shrink. Every guide pairs with a free tool that runs on your own device.
Every PDF carries the author, title and software that made it. Learn what it knows about you, how to check it, and how to strip it before you send.
Read the guide →Simple, advanced, qualified — what each level of e-signature proves, what US and EU law actually say, and when a drawn signature on a PDF isn't enough.
Read the guide →Government portals and job applications want exact caps. Here is the measured ladder: Medium lands you near 1 MB, Low near 500 KB, and when a cap is impossible, what to do instead.
Read the guide →GPS and EXIF location data hides in every phone photo. Strip it before you upload to dating apps so your address stays private.
Read the guide →One file to send or just a few pages? Learn when to merge and when to split, plus how to fix duplex scan page order.
Read the guide →Rejected for size, format, or background? Resize your signature scan to the form's pixels in one pass, free in your browser.
Read the guide →Big images slow Largest Contentful Paint and hurt Core Web Vitals. Resize and compress in one pass: smaller files, same quality.
Read the guide →Place a text mark in your browser before you post, with no upload and no quality loss — where it works, where it does not, and why it is not copyright protection.
Read the guide →Pre-compressing before sending made the file bigger (128.0 vs 111.9 KB) and blurrier. Document path: byte-identical, SHA-256 verified.
Read the guide →Measured from a 12 MP source: LinkedIn 400px is 5.3 KB, Instagram 320px is 4.5 KB, WhatsApp 500px is 7.1 KB. Circle crop hides 21.5%.
Read the guide →50 files, one drop: 3.6 seconds, 1.16 MB saved. The 10 already-compressed files were kept as original, which is the behavior to look for.
Read the guide →Network recording during a real compression session: 0 fetch, 0 XHR, 0 beacons. The 30-second DevTools test that verifies any tool, plus the honest limits.
Read the guide →Converted a 3-frame GIF: output kept only frame 0 and was 5x bigger. JPEG and PNG have no field for a second frame or a delay timer.
Read the guide →Vector text re-drew sharp at 72/144/288 DPI, but a 600x400 embedded image stayed 600x400 real pixels. Higher DPI cannot fix a low-res scan.
Read the guide →WebP starts with RIFF, JPEG with FF D8 FF. Renaming .webp to .jpg never changes those bytes, so strict apps still reject it. Only a re-encode works.
Read the guide →No-install routes compared. Tested: merging adds only 471 bytes per page, so a 28.7 MB photo set stays 28.7 MB. Size comes from resolution.
Read the guide →7 tested internal defects: the renderer recovered from 6, drew blank only for an empty content stream. Real causes are encryption, empty scans, or a viewer gap.
Read the guide →11 tested data URL cases: only 3 break the image (missing data: prefix, missing ;base64, doubled prefix). Newlines, whitespace and missing padding still load.
Read the guide →Tested side by side: form scan PNG 117 KB beats JPEG q90 122 KB, photo PNG 2.9 MB loses to JPEG 125 KB. Rule: text favors PNG, photos favor JPEG.
Read the guide →Why the viewer rotate button never saves, the /Rotate flag explained with byte-level proof, the duplex scan pattern (0,180,0,180), and the permanent fix.
Read the guide →Every guide on this page has a matching tool: no signup, no upload, files stay on your device.
Open the tools