Secure Tools is a privacy-first suite of browser utilities for everyday PDF and image work. Production tools process file contents on the user's device instead of sending them to an upload service.
The project is a static, category-first web application with no account requirement, backend, database, analytics, advertising, or telemetry.
- Process supported file contents locally with browser APIs and same-origin libraries.
- Make bounded, tool-specific privacy claims instead of promising complete anonymity or sanitization.
- Keep production processing free of file uploads, analytics, telemetry, remote codecs, and runtime CDNs.
- Vendor audited runtime dependencies on the Secure Tools origin where practical.
- Preserve clear resource limits, failure handling, keyboard access, responsive layouts, and six-language support.
- Keep source and Network-panel behavior inspectable.
See the privacy model for exact guarantees and boundaries.
- Images to PDF — arrange JPEG, PNG, and WebP images and save one PDF.
- PDF Merge — combine validated PDFs without rasterizing pages.
- PDF Split — extract ranges or produce per-page and fixed-interval archives.
- PDF Organizer — preview, reorder, rotate, remove, and export pages.
- PDF to Images — render pages to PNG, JPEG, or WebP.
- PDF Metadata Inspector & Cleaner — inspect and remove supported document-info fields.
- Image Converter — convert JPEG, PNG, and WebP batches.
- Image Resize — resize batches by pixels or percentage.
- Image Compressor — quality-compress images and compare byte results.
- Image Metadata Inspector & Cleaner — inspect supported metadata and save a verified cleaned copy without pixel re-encoding.
The Privacy hub links to the specialized Image and PDF metadata tools. It is a cross-category navigation surface, not a generic sanitizer. Scan/OCR and Media remain planned.
Detailed formats, limits, and behavior are listed in tool status.
Secure Tools includes English, Korean, Japanese, Spanish, German, and French interface catalogs. Theme choices are Light, Dark, and System. Language and theme preferences are the only application values stored in localStorage.
Serve the repository over HTTP so ES Modules load correctly:
python -m http.server 8000Open http://localhost:8000. Do not use a file:// URL.
Run the complete validation suite with:
node tests/run-all.mjsThe documentation index links to the maintained sources of truth for:
- architecture and delivery;
- privacy, local processing, and network boundaries;
- production dependencies and vendoring;
- search discovery, canonical metadata, and search-engine submission;
- production and planned tool status;
- release QA evidence;
- UX, accessibility, localization, and format-specific privacy audits.
Release history is recorded in the changelog. The current v2.0.0 line remains in pre-release observation.
Source: SecureToolsProject/Secure_Tools
See LICENSE. Vendored third-party code retains its own license beside each dependency.