We support OpenXML docx files, and legacy binary .doc files. We don't currently support RTF.
We only support Word documents at present.
No, our software does not require Microsoft Word in order to function. Not on the server, and not on the client. Instead, our software is built around our own independently developed high fidelity layout engine, which supports viewing, co-editing, and export (docx and pdf).
If you like what you see, you can build a proof of concept integration with your app. To get started, email firstname.lastname@example.org
We provide an Integration Guide which is customised to your environment, and SDKs for popular languages. Please email email@example.com.
Real time co-editing is coming soon! In the meantime, what happens is that the first user to open the editing link gets an editing session; other users who open the link are view-only (but see the any changes in real time).
Yes. Please see our Integration guide for examples.
No additional authentication or user credentials are needed to embed the editor. Your users don't need a Native Documents account. For more details, please see your Integration Guide.
A REST API provides access to all aspects of an editing session, including downloading the document as docx. Usually this function is called by your server backend.
Yes, you can choose to fetch the document from the Word File Editor in PDF format, using the REST API.
You can subscribe to our SAAS offering, or you can manage your own server. If you want to manage your own server(s), the Word File Editor server is available as docker containers which you start with docker-compose.
Yes. With our SAAS offering, you don't need to worry about this. If you choose to run your own server, you can run multiple instances of the Docker containers behind a load balancer (including for example, on AWS Fargate).
If you choose to self-host, you'll need skills around running Docker in production.