Does Fusial support Google Docs or PDF?
Fusial doesn't accept Google Docs or PDF files directly. This page explains why, how to convert each format into a supported .docx upload, and what trade-offs to expect.
Fusial doesn't accept Google Docs or PDF files directly — only .docx. You can still get the contents into Fusial by converting first.
Why Fusial can't read them natively
Fusial parses Microsoft Word's .docx format directly. When a counterparty sends a redlined contract back, Fusial reads Word's tracked changes out of the .docx and surfaces each one as an edit you can accept or reject. Neither Google Docs's native format nor PDF carries that information in a way Fusial can parse:
- Google Docs stores suggestions in Google's proprietary format. The export-to-
.docxstep is what makes the file readable to Fusial. - PDF is a presentation format — it captures how a page looks, not who edited what. Converting PDF to
.docxrecovers the text but loses tracked changes entirely.
Converting from Google Docs
- Open the contract in Google Docs.
- File → Download → Microsoft Word (.docx).
- Upload the downloaded
.docxto Fusial.
If you were collaborating with Suggestions turned on in Google Docs, those suggestions are preserved as Word tracked changes in the exported .docx — Fusial will see them.
Converting from PDF
PDF conversion has trade-offs. Choose based on whether the PDF was generated from Word or scanned from paper.
PDF generated from Word (digital text)
- Open the PDF in Word — recent versions of Word can open PDFs directly and convert them.
- Review the converted document carefully. Word's PDF conversion is not perfect: tables, headers, and footnotes often shift, and any tracked changes from the original Word file are not recovered (PDFs don't carry tracked changes).
- Save As
.docxand upload.
If you have the original .docx instead of the PDF, always prefer the original.
Scanned PDF (image of a paper contract)
- Run OCR on the PDF — Adobe Acrobat, ABBYY FineReader, or Word's built-in PDF import will do this.
- Carefully proofread the resulting text. OCR errors in numbers, dates, and party names can change the meaning of a clause.
- Save as
.docxand upload.
OCR'd contracts are a starting point for the AI, not a finished record. Always double-check AI extractions against the original PDF.
What about Apple Pages or other word processors?
Pages, LibreOffice Writer, WPS, and similar tools all export to .docx. Use their Export → Word (or Save As → .docx) option and upload the result.
Is native Google Docs support on the roadmap?
We hear this request often, but we don't have a date to share. Today the supported workflow is:
- Export from Google Docs as .docx (File → Download → Microsoft Word).
- Upload the .docx to Fusial. Tracked changes, comments, and formatting are preserved.
- When you're done, export the redlined .docx from Fusial and re-upload it to Google Docs if you want to continue editing there.