Data-flow map
The path is short: selection → file-signature check → browser memory → decoding → bounded processing → output check → download. Exact Size Tools does not send the selected file to an application server during these operations.
- Images: browser decoder and canvas, followed by a downloadable file whose format and dimensions are checked
- PDFs: a local library loaded from this site, followed by a new PDF whose header and page count are checked
- Temporary previews: object URLs revoked when replaced or cleared
- Logs and optional analytics: selected file details are never included; Google services load only after visitor consent
Safety limits
Byte, pixel, file-count, and page-count limits reduce the chance that a damaged or unusually large file will exhaust browser memory. The tool checks the file signature before decoding it and stops on unsupported, corrupt, encrypted, or infeasible input. These controls reduce avoidable risk, but they are not a substitute for keeping an untouched original or using a trusted device.