How PDF Export Works

A PDF export is a report for one saved project version. It is generated from stored result data, not from a screenshot of whatever happens to be on screen.

Export model

The export model is backend-generated PDF output based on stored project-version results. One export represents one specific project version, with its scenarios, warnings, and report structure tied to that saved result set. If a version has not been calculated yet, there is nothing meaningful for the export layer to render.

The report follows the saved scenario type. An AC result, DC distribution result, mixed AC/DC result, and solar-enabled result do not all contain the same sections. The PDF should be read as a report of the stored result that was calculated, not as a generic template that always contains every possible output area.

Access and context

PDF export is part of the paid report workflow. Personal access depends on the paid plan attached to the account. Workspace report access depends on the active workspace, its billing state, and its access rules. If export is missing, check the plan and the current context before assuming the calculation is broken.

Report boundary

A polished report is still a preliminary sizing output. It is not a certified engineering design, procurement specification, or installation sign-off.

Exporting also does not pull in unsaved edits from the scenario editor. If you have changed scenario settings, loads, solar settings, installation inputs, or usage inputs, calculate and save the version again before exporting.