Help center
quickstart - FAQ - troubleshooting - billing - GDPR - contact
1. Go to the free trial. 2. Drop a file. 3. Done.
Files under 1 MiB run on our EU servers (deleted after the job). Larger files stream to the server over TLS, are processed in RAM, and deleted immediately after the job (resumable upload sessions and temporary artifacts are removed within 6 hours). The compressor races several codecs (including xz, zstd, and brotli) in parallel; the smallest result wins, and the restore is byte-exact.
Yes. Every result is roundtrip-verified by SHA-256 at the codec level. Decompressed output is bit-identical to the input - no lossy re-encoding, ever. This is a guarantee about the roundtrip of Pedulli's own output.
Pedulli is a best-of-N racer, not a single algorithm. It races xz, zstd, brotli and your data's SRD math, then keeps the smallest verified output - so it is never larger than the best standard codec (worst case +1 byte). On many structured data classes (JSON, MP4, logs, periodic binary, domain-shaped archives) one of the racers finds redundancy a single generic codec misses, and Pedulli wins outright. On already-optimal or random data it simply selects the best codec - a tie at that codec's size, never a loss. See the measured benchmarks.
Pedulli adds at most +1 byte - a single tag byte for the identity fallback. That is the never-worse floor on Pedulli's own output: the result is never more than 1 byte larger than the input. (For comparison, common codecs add a few to a few hundred bytes of overhead on incompressible input.)
No. Server-side processing holds the file in RAM only and deletes it immediately after compression. No retention of file content, no content logging, no tracking cookies. See the privacy policy.
For files larger than 16 MiB, your browser splits the file into 32 MiB chunks and uploads them resumably. The server reassembles the full file before compression, so the ratio is identical to a single-shot upload - no cross-chunk redundancy loss.
Yes. Drag a folder onto the compress box - Pedulli packs it into a tar archive in your browser (streaming, no full-RAM materialisation even for multi-GB folders) and then compresses the tar with the racer.
.pdli is the Pedulli container: a 1-byte tag plus payload. Decompress it with the Pedulli web UI or (planned Q3 2026) the native CLI.
Free tier: up to 100 MB/file, no signup for the browser trial, plus a free API key with a token balance. Pro: EUR49/mo with 10 GB included, per-GB after. Token top-ups and Enterprise / on-prem are also available. See pricing.
14-day no-questions-asked refund on monthly Pro. EU consumer protections per Italian law (D.Lgs. 206/2005). See the terms of service.
Two paths today: (1) hit the REST API with your key (see the API docs), or (2) on-prem / source license for Enterprise (book a call). A native CLI is planned for Q3 2026.
Free tier per-IP limits during the public window: 60 compress + 60 decompress per minute. Paid tier uses account-keyed limits. Create a key on the signup page and manage it in your dashboard. See the docs.
No. The witness-gated exact verifier only checks witnesses you supply (SHA-256 roundtrip, AES-GCM re-encryption match, p*q==N integer check, supplied-clause SAT). It verifies; it does not solve, crack, or break RSA, AES, ECC, or any cryptography. See the witness explainer.
Open a ticket at pedulli.io/feedback.html - include the file size, MIME type, and (if not confidential) a small repro sample.
EU-sovereign. Server in Falkenstein (DE), Hetzner. No retention of file content. GDPR by design. Italian-built. See privacy and terms.
pip install opentimestamps-client ots upgrade MANIFEST.txt.ots ots verify MANIFEST.txt.ots
Reports the Bitcoin block height and timestamp at which the manifest hash was committed. Downloadable manifests are on the verify page.
Direct: francescopedulli@gmail.com - Forli, Italy (GMT+1)
Bug / feedback: pedulli.io/feedback.html
Status / outages: pedulli.io/status.html