Feature Request: Support direct-to-storage image uploads for DOCX import (serverless-friendly)

[goteam-joshclaudio]

Description

Tiptap Convert’s DOCX import with preserve-images requires providing an imageUploadCallbackUrl that the conversion service POSTs image files to:

This workflow works for traditional backends, but is incompatible with serverless architectures (e.g., Laravel Vapor, AWS Lambda, Vercel) because:

• API Gateway / serverless endpoints have strict body size limits (~6–10 MB)
• No support for streaming uploads
• Direct-to-object-storage (S3, Cloud Storage, etc.) is a common pattern for modern apps

Currently, there is no way for the conversion service to directly upload images to storage without routing through a traditional server endpoint.

Use Case

For serverless-first applications, large DOCX files containing images cannot be imported using the current imageUploadCallbackUrl flow without hitting serverless limits. A storage-agnostic upload mode would allow the conversion service to:

1. Request a pre-signed upload URL for each image
2. Upload the image directly to object storage
3. Return the final public URL to Tiptap Convert

This enables serverless backends to fully support DOCX image preservation, avoids body size limits, and reduces server bandwidth and operational complexity.

Type

New feature

[alexvcasillas]

Hey @goteam-joshclaudio thanks for the feature request! Sure indeed seems like a great addition and I’ll have it on my backlog to implement this mechanism so you can generate and provide a pre-signed upload URL for each of the images in your document :)