Document conversion guide

Supported conversions

Choose, convert and review

1. Open a workspace, wait for the service connection, choose a supported file and keep the total upload within 5 MB. Complete the security check before converting.
2. For Images to PDF, select up to 20 individual images together, or one flat ZIP. Their selected order becomes the page order.
3. Convert once, read any conversion notes, and review the output before sharing or printing.
4. For worksheet exports, download each CSV independently. Download all as ZIP remains optional; a ZIP app is not required for individual downloads.

Limits and safety

5 MB total upload, 20 MB output, 20 PDF pages and a 60-second processing timeout. Text/data conversions also enforce character and cell limits. CSV imports allow at most 1,000 rows, 100 columns, 50,000 cells and 32,767 characters per field. Image limits include 12 million pixels per image.

Old binary DOC/XLS/PPT formats, OCR, password-protected input PDFs and arbitrary HTML are not supported by these endpoints. Formula-like CSV exports are prefixed for safer initial spreadsheet opening; re-saving CSV in another application can change that protection.

Where your document goes

The 20 browser tools process document contents in your browser. The 12 new conversions use FourAPI: document bytes leave the browser and are sent to a separate Python service. The conversion service runs on Render, configured in Frankfurt. Document uploads and responses travel directly between your browser and the FourAPI endpoint, without a FourPoint website conversion proxy. The service processes them in memory and stores separate quota/request metadata in Supabase, not document files. Cloudflare Turnstile checks the public conversion session before upload. Downloads remain where you save them. Host swap, crash dumps and infrastructure logs need separate deployment controls.

The workspace checks actual service availability and may wait while Render wakes up. Public website usage shares a daily website allowance and the service’s global capacity, so availability is not guaranteed. Failed admitted attempts count towards these safeguards. Do not automatically repeat an interrupted conversion: its processing may have completed. No permanent API key is stored in public website configuration.

Request a signature

Self-signing stays on your device. Request Signature creates separate private recipient and requester links and temporarily uploads the PDF to the FourPoint backend’s private Cloudflare R2 storage. This is separate from FourAPI conversions. Maximum: 5 MB and 20 pages; compress larger PDFs before uploading. The backend rejects oversized files rather than automatically altering them.

Recipients review the original PDF and draw a signature at the requester’s fixed position. Share only the recipient link. Save the requester link to check status, download the signed document or revoke access. No email is sent automatically and links do not verify identity. This provides a visible signature image, not a qualified electronic signature or cryptographic signing certificate.

Unsigned links expire after 24 hours. Completed requests expire after 1 hour or the original deadline, whichever comes first. Access ends at expiry; scheduled cleanup runs every 15 minutes and retries failures to delete files and request metadata. Download your copy before expiry. See the privacy policy for the full storage and deletion details.

Document lifetime and deletion

FourAPI intentionally creates no uploaded or converted document files. Bytes pass through memory and Python worker pipes. The worker exits when conversion finishes or is stopped after the 60-second processing deadline. Upload, response transfer and parent-process memory have separate lifetimes; this is not a promise of secure erasure exactly 60 seconds after upload.

Result previews and download links are held in your browser and cleared when replaced or when you leave the workspace. Downloaded copies stay on your device. Separate conversion metadata is eligible for request-driven cleanup after 30 days; it does not contain document contents or uploaded filenames. Provider buffers, infrastructure logs and backups have separate controls. Read FourAPI privacy and retention details.

Developer API

Developers can apply for individual API access at FourAPI. The developer portal provides backend integration examples, private API keys and usage information. Keep developer keys in your server environment.

The API accepts raw bytes at POST /v1/convert/<tool-slug> using application/octet-stream. Developer keys stay in trusted server environments; the public FourDOC website obtains short-lived, single-use tokens bound to the selected tool and getfourpoint.com after a verified security check. Append ?output=files for JSON containing independently downloadable file contents, MIME types, sizes and base64 data. This performs one conversion without retained server download files.