Compress PDF to 100KB

A 100KB PDF is a demanding target. It can suit a short certificate or a simple single-page document, but it is not automatically appropriate for every application. Start by reading the active upload field and official notice. Confirm that the limit applies to the complete PDF, not each page, and check whether colour, greyscale, page count, or document orientation is specified.

FileGizmo treats 100KB as a maximum of 102,400 bytes. The browser worker renders the pages locally, rebuilds them as compressed page images, and tests multiple resolution and JPEG-quality combinations. It keeps the clearest candidate that fits. The result panel then reports page count, actual size, selected ceiling, and the render scale used. This is a measurable acceptance check rather than a decorative compression percentage.

The tradeoff is explicit. Rasterization changes the internal structure of a PDF. Selectable text becomes pixels; clickable links, editable forms, comments, layers, attachments, and digital signatures are not preserved. That makes this workflow suitable for visual upload copies, not archival masters, signed contracts, accessible documents, or forms that still need editing. Keep the original file separately.

Before processing, remove pages the portal did not request and correct rotation. Crop excessive scanner borders where doing so does not remove stamps or annotations. A clean one-page certificate spends its limited bytes on meaningful detail; a scan surrounded by a large desk or black border wastes them. Do not crop official headers, registration numbers, seals, QR codes, dates, or signatures.

After downloading, open the result at normal size and zoom in. Read every name, number, issuing authority, date, and category. Check fine stamp edges, QR modules, and signature strokes. If a detail is ambiguous, the file has not passed a practical quality check even when its byte count passes. Choose a larger official limit or split the document if the portal permits it.

FileGizmo refuses targets that allocate too few bytes per page and reports when its minimum practical candidate still cannot fit. That failure is useful: it prevents a misleading success state and tells you the document needs a different preparation strategy. A strict byte number should never override legibility or the destination’s actual instructions.

The official-source panel near the tool shows several current document-specific examples and verification dates. Those rows illustrate why there is no universal government-exam limit. Always open the linked notice and confirm that it matches your exam, document, and cycle before submitting.