A practical guide to browser file tools

Start with the outcome, not the extension

A JPG can be too large, the wrong dimensions, in the wrong format, or unsafe to share; those are four different problems. Likewise, a PDF may need compression, page extraction, merging, or conversion. Pick the operation that matches the failure you are trying to fix, then preserve the original until you have checked the result. Repeatedly converting or recompressing a file can discard detail without solving the real constraint.

Browse all tools → See the current Pixo suite grouped by compression, resizing, conversion, PDF, privacy, generation, and editing.

Image work has three separate stages

Compression changes how efficiently image information is encoded. Resizing changes the pixel canvas. Conversion changes the container or codec. A web photo may need all three, but the order matters: crop or resize to the required dimensions, choose an appropriate output format, then compress and inspect the final result. For a form with a strict file-size ceiling, a target-size compressor can search for an acceptable setting; for a website, controlling dimensions often removes more waste than repeatedly lowering quality. Keep transparency in mind when moving from PNG or WebP to JPG, and remember that converting a lossy source to a lossless format cannot restore detail already discarded.

• Use format-specific compressors when the format must stay unchanged.
• Use resize or crop tools when the rejection is about dimensions rather than bytes.
• Use conversion only for a real compatibility or delivery requirement, not as a default cleanup step.

PDF tools solve document problems, not image problems

PDF is a page-oriented document format that can contain text, vector artwork, embedded fonts, forms, and images. Compress PDF is appropriate when a document exceeds a mail or portal limit. Merge PDF combines page sets; Split PDF extracts or separates pages; PDF to JPG rasterizes pages for systems that only accept images; JPG to PDF packages image pages as a document. These operations have different consequences. Rasterizing may make text harder to search or copy, while aggressive compression can reduce the legibility of scanned text. Open the downloaded PDF, move through every page, and confirm page order, orientation, selectable text, links, and small print before deleting the source.

• Keep an untouched original when the document is contractual, archival, or difficult to recreate.
• Prefer splitting when the recipient only needs selected pages; it can be clearer than compressing the entire document.
• Zoom in on signatures, tables, and scanned text after any size-reduction pass.

Privacy requires both metadata checks and visible redaction

Privacy is not one switch. A photo may carry EXIF fields such as capture time, camera information, or location data, while a screenshot or document page may visibly expose names, account numbers, message previews, or faces. Metadata removal addresses embedded fields. Redaction addresses pixels that a viewer can see. A cosmetic blur or overlay is not sufficient if the exported file can reveal the original layer underneath, so verify the flattened downloaded result. Also review filenames, QR codes, reflections, browser tabs, notification banners, and page margins; privacy leaks often sit outside the region that first drew your attention.

• Use the EXIF viewer to inspect what is present before deciding what to remove.
• Use metadata removal for embedded fields and the redaction tool for visible content.
• Reopen the exported copy and try to zoom, select, or uncover sensitive areas before sharing it.

Generators turn specifications into repeatable assets

Generator tools are useful when the output is a set or specification rather than a one-off edit. A passport-photo workflow helps frame a portrait for a selected template, but it cannot guarantee acceptance by every authority; compare the result with the current rules of the receiving agency. An app-icon generator creates the common size variants from one source, yet you should still inspect the smallest icons for legibility. A responsive-image generator produces multiple image widths and markup guidance for web delivery. A QR code generator encodes text or a URL into a scannable image, so test the exact downloaded code with more than one device before printing or publishing it.

• Begin with a clean, high-resolution source because every generated variant inherits its defects.
• Check the destination's current specification instead of assuming a preset is universal.
• Test functional outputs—especially QR codes and responsive markup—outside the generator preview.

Editing tools are for deliberate visual changes

Cropping, rotation, background removal, and general image editing change the visible composition rather than only the file's encoding. Use crop to control framing and aspect ratio; rotate when orientation metadata or capture position is wrong; remove a background when the subject needs transparency or compositing; use the image editor for combined adjustments. Work from a duplicate when the edit is difficult to reverse. After export, inspect edges, hair, shadows, text, and transparent regions against both light and dark backgrounds. A technically valid download can still be unsuitable if the visual edit removed context or introduced a halo around the subject.

File transfer is a live connection, not another conversion

Send Files is for moving the original file bytes to another browser. It uses a WebRTC data channel: signaling helps the two browsers establish a session, and network traversal infrastructure may relay encrypted traffic when a direct peer path cannot be established. That is different from uploading a file as a stored cloud object, but it still uses the network and requires both sides to stay connected during the transfer. Confirm the recipient and room details through a trusted channel, keep both tabs open, wait for completion, and compare the received filename and size before closing the session.

• Do not use transfer as a substitute for redaction or metadata removal; prepare sensitive files first.
• A transfer can fail when either browser sleeps, changes networks, closes the tab, or loses connectivity.
• For important material, the recipient should open the file and confirm it is complete before either side leaves.

What local browser processing does—and does not—mean

Pixo's image, PDF, privacy, generator, and editing operations are designed to process file content in the browser rather than sending it to an application server for transformation. The browser still loads the website's code and ordinary web resources, and installed-app features may keep settings or temporary artifacts on the device. Send Files is intentionally different because its purpose is network transfer to another browser. Local processing reduces exposure to a remote transformation service, but it does not replace device security, trusted recipients, safe backups, current browser software, or a careful review of the exported file.

• Close unrelated sensitive tabs and use a device you trust for confidential work.
• Treat the downloaded result as a new file and verify it independently from the on-page preview.
• Keep originals until the destination accepts the output and you are certain no further correction is needed.

A repeatable finish-check prevents most mistakes

A good file workflow is short: identify the destination's requirement, duplicate the source, perform the smallest necessary operation, download the result, and validate it in the destination or a separate viewer. Check bytes, dimensions, format, page count, visual quality, metadata, and privacy only where they matter to the job. If the result fails, return to the original rather than repeatedly processing the previous output. That keeps quality loss, accidental disclosure, and confusing filenames from accumulating across attempts.