# Frequently asked questions

Answers about previews, publishing, quotas, and PDF render results.

## Does preview consume quota?
No render quota. Run is a real render and consumes quota on success. Resource/time policies still apply to preview.

## Must I publish before API rendering?
Yes. Real rendering needs a published version; drafts remain previewable.

## Is one editor page one PDF sheet?
Not necessarily. A logical page can flow across several sheets.

## Does rendering accept a slug?
No: `template_id` requires the template UUID.

## Is the PDF ready after POST?
No. HTTP 202 acknowledges the job. Follow status and download on success.

## Does published mean locked?
No. A published version remains editable. Saving changes can affect later jobs using that version. Create a separate version when preparing a design change for a live integration.

## Can MCP publish and produce a real PDF?
Project MCP has no publish or durable-render tool. Agents can edit and visually preview; use the app and render API for publication and real output.

## Can I load any image or JavaScript?
Public HTTPS image access depends on plan/resource policy. User JavaScript, arbitrary external CSS and arbitrary remote fonts are not supported.

## Is output retained forever?
No. Download important output into your own storage.

## Why are upgrade/invitation controls missing?
Beta currently has no self-service upgrade/downgrade/cancellation controls. **Settings** shows plan and usage. **Members** currently lists existing members and roles; it has no invitation controls.