Get back to creating. We’ll help with the rest.

Use the support form above for Presenton Cloud bugs, billing questions, account access, API problems, or an issue that contains private information. Use the Presenton GitHub issue tracker for reproducible bugs in the open-source project. For private deployment planning, enterprise infrastructure, or implementation requirements, contact our sales team.

We typically send an initial reply within 24 hours. Complex API, account, billing, or file-specific issues may require additional investigation after the first response.

Include whether you use Presenton Cloud or the open-source version, what you were trying to do, the steps that reproduce the issue, what you expected, and what happened instead. Add the affected page URL, Presenton version, browser or deployment environment, and sanitized screenshots or error messages when relevant.

Yes. Tell us whether the issue occurs during import, editing, preview, or export. Include the affected format, the application used to open the result, and a description of the incorrect slide or element.

Report reproducible bugs in the open-source Presenton project through the Presenton GitHub issue tracker. Before creating an issue, search for an existing report and include your Presenton version, deployment environment, reproduction steps, expected behavior, actual behavior, and sanitized logs. Use the support form above for Presenton Cloud bugs, billing, account access, or anything containing private information. For private deployment planning or implementation, contact sales.

For a new private-cloud, VPC, on-premise, or restricted deployment, contact our sales team to discuss architecture, security, integrations, implementation, and support requirements. If you already have an enterprise deployment and an agreed support channel, use that channel for operational incidents.

State whether the error occurred in Presenton Cloud or an open-source deployment. Include the endpoint, response status, approximate request time, Presenton version, a request identifier when available, and a minimal sanitized request example. Remove authorization headers, API keys, tokens, and confidential presentation content.

No. Never send passwords, one-time codes, API keys, access tokens, full payment-card details, or private credentials. Replace confidential presentation content with a reduced or sanitized example before sharing it.