Uploading a document

Upload your documents to EveryPage using the drag-and-drop uploader or file browser. The platform accepts PDFs directly, plus Word and PowerPoint documents that are converted to PDF automatically in flight.

Supported file types

EveryPage accepts the following file formats:

• PDF (.pdf) — uploaded directly
• Word (.docx) — converted to PDF automatically (requires conversion enabled)
• PowerPoint (.pptx, .ppt) — converted to PDF automatically (requires conversion enabled)
• Legacy .doc — not supported; save as .docx in Word or export as PDF

If the server has Office conversion enabled, the uploader displays "Drop your document here." When conversion is disabled, only PDFs are accepted and the uploader shows "Drop your PDF here."

Query the endpoint GET /api/upload/options to check whether the server accepts Office documents and what the format-specific size caps are.

File size limits

Upload and storage limits depend on your subscription plan:

These limits apply to the final stored file. For Office documents, source-format caps differ:

• Word documents — up to 25 MB before conversion
• PowerPoint files — up to 50 MB before conversion

If your source document exceeds its format cap, export it as a PDF and upload that instead.

How the upload works

When you upload a file, EveryPage:

1. Streams the file — the entire file is never held in memory at once; bytes flow from your browser directly to the server and into encrypted storage
2. Converts Office documents — if you uploaded .docx, .pptx, or .ppt, the server streams it to the document conversion service and takes back a PDF, before encryption
3. Encrypts — the file is encrypted with AES-256-GCM and written to disk in chunks
4. Verifies size — once encrypted, the file is checked against your plan's storage cap (the converted PDF size is what counts for Office files)

If any step fails — the file is corrupted, the conversion service is down, or the final size exceeds your limit — the upload is aborted and no partial file is stored.

Conversion failures are reported with a specific status: 413 when the source exceeds its format cap, 422 when the document could not be converted, and 503 when the conversion service is unreachable. In each case the response body carries a message you can act on.

What you get back

After a successful upload, the response includes:

• UUID — the canonical identifier of your file, used internally and in API calls
• Short ID — a 12-character base62 alias for sharing, always containing at least one uppercase letter; the shareable link is /{shortId}
• Share URL — a complete, ready-built link you can send immediately (e.g., https://everypage.co/Ab3xY9kQ2mZ7)

For anonymous uploads (no account):

• Claim token — a stateless signed token, valid for 30 days, that lets you attach the file to an account later from any browser session
• Manage token — a separate signed token that authorizes the settings write endpoint (PUT /api/v1/files/{uuid}/settings) for as long as the file stays unclaimed; a token caller gets free-tier fields only

Anonymous uploads and expiry

Documents uploaded without an account are shareable by link immediately — anyone with the link can view it. These files are kept for 365 days before automatic deletion. If you sign up or log in from the same session, the file is claimed into your account. Claiming preserves the existing deletion date; you can then set a different expiry, up to the cap your plan allows.

For per-plan limits and details on claiming uploads, see Anonymous uploads and claiming.

Next: Configure and share

After upload, you land on the Configure & Share screen where you can:

• Set a share link password or email gate
• Choose a viewer mode (standard, flipbook, magazine, swipe)
• Generate a QR code
• Create an embed code
• Set view limits or expiry dates

See Configure & Share for details.

Conversion details

When you upload Word or PowerPoint files, EveryPage converts them to PDF before storage. The stored file is an ordinary PDF, so every downstream feature — the viewer, watermarking, readership — behaves exactly as it does for a directly uploaded PDF. The stored name takes the .pdf extension too: report.docx is stored as report.pdf.

Before conversion, the server checks the file's container signature: .docx and .pptx must be OOXML (Zip) files, and legacy .ppt must be an OLE2 compound file. A file whose contents do not match its extension is rejected rather than sent to the converter.

If conversion fails, exporting the document as PDF in Word or PowerPoint and uploading that works around the issue.

For more on format-specific conversion, see:

• Word to PDF
• PowerPoint to PDF