Frequently asked questions

No. Up to five emails per day can be converted without registration. The limit uses a cookie in this browser and resets at midnight UTC; clearing browser data may reset the anonymous identity.

Individual EML, MSG, MBOX, PST and OST files, plus ZIPs containing supported messages.

• PST and OST containers are unpacked into messages under the same limits.
• An upload is limited to 1000 source files and 500 MiB total, with a 50 MiB per-file cap and a 1000 MiB / 2000-entry archive expansion limit.

It depends on the format you pick at conversion time.

• PDF only gives one file — several messages become a single chronological PDF with a contents page.
• PDF + attachments is a ZIP of the message PDFs and the original files, without indexes or reports.
• The full archive carries a PDF for each processed message, the preserved attachments, Excel and CSV indexes, an error report, README and optional SHA-256 hashes.
• Supported PDFs, images and TXT attachments can be appended to each email PDF.
• You can also add one chronological merged PDF with a contents page and Bates page numbering.

Yes.

• The PDF/A-2b option re-encodes every PDF with Ghostscript: fonts are embedded and interactive elements are dropped.
• If re-encoding fails for a file, the archive keeps a regular PDF and the manifest records the state.
• Conformance is not checked by an independent validator — do not treat it as proof of archival status.

Yes.

• A stamp goes onto every PDF page: the presets CONFIDENTIAL, PRIVILEGED and DRAFT, or your own text of up to 40 characters, and it also appears in the merged chronological PDF.
• A template picks standard, clean (no service footer) or branded, with a company name of up to 60 characters in the footer.
• Both options change presentation only: the message content stays the same, and a stamp by itself does not make a document confidential or privileged.

Yes.

• The team package runs for 30 days and is renewed manually; three days before it ends, the organization owner receives a reminder email with a renewal link.
• While the package is active, members can be invited into the organization and conversions spend from one shared credit wallet.
• Details are on the pricing page.

No. Files are transferred over HTTPS and processed on the server.

• Default AES256 encryption has been confirmed in the live object storage.
• This is not an audit of the entire infrastructure or a guarantee that every kind of correspondence can be handled safely.
• Russian and English versions currently share the same server infrastructure; language selection does not determine the processing country.
• Infrastructure providers, storage countries and administrator access locations have not yet been published and require operator confirmation.
• We cannot currently promise a specific data location or the absence of cross-border processing.
• Until these details are confirmed, do not upload data that requires a particular processing location.

Remote resources are blocked by default. Safe CID images included in the email can be processed by the server worker.

Yes. After the free daily allowance you can buy a credit package on the pricing page; payment is by card through Robokassa, and a receipt is issued after the payment is confirmed, where required by local law.

No. PDFs and hashes help organize and compare files but do not prove authenticity, completeness, legal admissibility or chain of custody.