Our Processing Architecture: Client-Side vs. Server-Processed
Every tool page on Toolcolabs displays a badge showing how your files are processed.
Unlike websites that claim "100% client-side" for every page while silently uploading files to a backend API, Toolcolabs documents the exact processing mode of each utility:
- Processing: In your browser (HTML5 Canvas / Local JS): Applies to the entire Emoji & Symbol Copy Library (
/emoji/*), JPG to WebP (/tools/images-converters/jpg-to-webp), and PNG to WebP (/tools/images-converters/png-to-webp) on browsers supporting nativecanvas.toBlob('image/webp')(Chrome, Edge, Firefox, Brave, Opera). On Safari/iOS where WebKit does not natively export WebP from HTML5 Canvas, our WebP tools automatically fall back to our encrypted HTTPS API so Safari users still receive valid.webpfiles. In addition, PDF page-count inspection and page thumbnail previews before merging or splitting are rendered locally in your browser usingpdfjs-dist. - Processing: Server-processed (Encrypted HTTPS + 30-Minute Auto-Deletion): Applies to image format converters requiring multi-format decoding/encoding (such as JPG to PNG, PNG to JPG, HEIC to JPG, WebP to JPG/PNG, AVIF, BMP, GIF, TIFF, SVG, ICO, and Image/PDF conversions), image compression and resizing tools (Compress Image, Target KB Size, Resize, Crop, Aspect Ratio, Passport Photo, Social Media Resize), image editing tools (Rotate, Flip, Grayscale, Brightness/Contrast, Blur Background, Change Background, Watermark Add/Remove), and PDF document tools (Merge PDF, Split PDF, Compress PDF).