PDF export ignores user timezone setting for date macro output

Direct Answer

No. The Confluence PDF/Word export API does not expose a documented timezone parameter that overrides the server default for Date macro rendering, and there is no supported mechanism to inject the initiating user's profile timezone into the export rendering context on Data Center. Cloud is subject to the same server-side export limitation, though internal multi-tenant handling may differ from Data Center.

Confirmed Facts vs. Likely Explanation

Confirmed: Confluence persists timestamps in UTC. The web UI converts those timestamps to the viewing user's configured timezone at presentation time. The export pipeline runs as a separate server-side rendering pass that does not carry the requesting user's timezone preference into the macro renderer, so Date macros resolve against the server clock or UTC.

Likely but unconfirmed: Whether any undocumented export context keys exist in specific 7.x or 8.x builds. Atlassian has not published an export rendering-context parameter for user timezone, so relying on undocumented keys risks breakage across point releases. Cloud and Data Center may differ in available export hooks; feature parity should not be assumed.

Practical Workarounds

1. Browser print-to-PDF: Print the UI-rendered page from the browser. This preserves the user's timezone conversion because it bypasses the server-side export pipeline entirely.
2. Server timezone alignment: If your organization operates in one primary timezone, set the JVM system timezone to match so exports are consistent for the majority of viewers.
3. Explicit date formatting: Where possible, use macros or add-ons that accept a hard-coded timezone offset so the rendered string is unambiguous regardless of export context.

Note that pre-rendering via the UI does not fix relative-date logic (for example, "2 days ago") inside the export pipeline, because the macro still resolves relative to the server clock during export.

Verification

To confirm the pipeline gap on your instance:

1. Create a test page with a Date macro configured for a relative date.
2. Export to PDF as two users with distinct profile timezones (for example, UTC+0 and UTC+8).
3. Diff the resulting timestamps. Identical output confirms the export ignores user context.
4. Inspect the export request in browser dev tools for timezone headers or context objects. If you want to probe for undocumented support, append a timezone query parameter to the export URL and verify whether macro output changes or the request errors; treat any success as version-specific and unsupported.

Missing Diagnostic

Provide the exact Confluence version (for example, 8.5.x) and whether you are using the native export or a third-party PDF add-on. This determines whether a version-specific rendering-context workaround is worth investigating or whether the browser-print path is the only reliable option.