The open GPDoc file remains the working source. Exporting, sharing, or publishing creates a new destination or an online collaboration state. The available actions depend on the file type and client.
Export a local file
Open File > Export. The export window lists the output formats supported by the current file type.
HTML, PDF, and Microsoft Word are available across editable GPDoc file types. Documents, slides, notebooks, scripts, and drawings also expose Markdown output. The file-type-specific options include:
| GPDoc file | Additional local output |
|---|---|
| Document | LaTeX |
| Slides | LaTeX and Microsoft PowerPoint (.pptx) |
| Notebook | LaTeX and Jupyter Notebook (.ipynb) |
| Script | LaTeX and the original source extension |
| Dataset | CSV |
| Drawing | SVG and PNG |
In the web app, File > Save File downloads the complete GPDoc JSON source as .gpdoc.json. Save File and Export are separate actions.
PDF output can open the browser or operating-system print workflow. Complete the final file save in that system dialog.
Send a copy to Google Docs or Microsoft 365
Open File > Export, choose the Google or Microsoft destination, and authorize the provider when prompted.
- Documents can create supported Google Docs or Microsoft Word copies.
- Slides can create supported Google Slides or Microsoft PowerPoint copies.
- Provider workflows can expose create, linked update, open, or share actions depending on the file and current client.
The provider copy remains separate from the Markdown or GPDoc source.
Share with collaborators
Open File > Share Document on a supported file. Add collaborators and choose the available role. Shared files are stored online so the live room, comments, suggestions, presence, and save state can be available to authorized participants.
Sharing is not the same as exporting a PDF or HTML file. A collaborator joins the live GPDoc file; an export is a detached copy.
Save to a Gist or GitHub repository
Open File > Cloud Storage and choose the applicable destination.
- Save a public or private Gist.
- Save to an authorized GitHub repository and path.
- Keep the GPDoc source plus the destination files exposed by the selected save workflow, such as HTML, Markdown, CSV,
.ipynb, or script source.
Repository access, branch protection, organization policy, and visibility still apply.
Publish a website with GitHub Pages
Open File > Publish and choose the GitHub Pages workflow for a supported file. GPDoc creates HTML, writes it to the selected repository path, and configures the supported repository publishing action. GitHub owns the Pages deployment and final public URL.
You can also export standalone HTML and place it in a separate static-site workflow. GPDoc does not provide custom-domain publishing or operate an external hosting account for you.
Review before sharing
Check every exported or published copy. Do not include credentials, private customer content, or restricted files in a public Gist, repository, or GitHub Pages site.
For local and shared-file storage boundaries, see Local files and online shared files. For Codex and Claude Code, see Use GPDoc with coding agents.
Next guide
Custom-domain publishing
GPDoc does not provide custom-domain publishing. Use GitHub Pages or export HTML for a separate hosting workflow.