Experiencer documentation
Exporting and printing
Save portable JSON, export HTML and CSS or PNG, print to PDF, and understand the Pro saved-resume PDF workflow.
Last reviewed:
Save an Experiencer JSON file
Choose File → Save As to download the current document in Experiencer’s JSON format. This is the best editable backup because it preserves the document tree, page settings, fonts, images stored in the document, and document-authored styling expected by the editor.
Use File → Load to open the file later. Do not edit the JSON by hand unless you can validate the schema and keep a known-good copy.
Export an HTML and CSS package
Choose File → Export HTML/CSS package for a browser-readable copy of the rendered résumé and its styles. The package is useful for inspection or controlled hosting, but it is no longer an Experiencer working document. Keep the JSON file if you plan to continue editing.
Review external image and font references before sharing the package. A recipient’s browser may request those resources from their hosts.
Export a PNG
Choose File → Export to PNG to render the current résumé pages as an image. The export modal provides copy and download controls when supported by the browser.
PNG is useful for visual previews, not for ATS submission. Text inside an image is not normal extractable document text.
Print or save as PDF
- Choose File → Print.
- Review the résumé in the browser print dialog.
- Select a PDF destination when you want a PDF file.
- Disable browser headers and footers, use the intended paper size, and enable background graphics if the template requires them.
Printer settings vary. Inspect the saved PDF for page count, clipping, fonts, links, background colors, and selectable text.
Export the latest saved cloud résumé through MCP
Pro An authorized MCP client can request a PDF of the latest saved non-template cloud résumé after you explicitly request or approve that export.
The generated download is short-lived and represents the saved server version. Unsaved editor changes are excluded. The connected assistant may offer the workflow, but it should not create the artifact until you ask for it or accept the offer.