Cloudscript Typst Renderer
Cloudscript Typst Renderer is a Confluence Cloud app, built on Atlassian Forge, that renders Typst source and the mathematics Typst is known for directly on a Confluence page. You paste Typst source into the macro's configuration, and the document is compiled and drawn in the reader's browser when the page is viewed. Because the page holds the source, each view renders it afresh, so an edit to the source is what the next viewer sees.
Typst is a typesetting language covering the same ground as LaTeX. If your team maintains a LaTeX-screenshot workflow for maths in Confluence, this macro replaces it with source that renders on the page: mathematical notation is set in Typst's own maths font, as vector output you can select and zoom, alongside the headings, prose, tables and code that make up the rest of a Typst document.
Every document is compiled in your browser, not on a server, and is never sent to Cloudscript.io or any third party; the app requests no Confluence permissions and stores nothing outside the macro on your page. Because this security posture keeps rendering on the live page, a page exported to PDF or Word cannot display the macro's content in its rendered form; the export carries the Typst source instead. The macro also renders self-contained documents only, without package imports or external images.
Adding a document
Edit a Confluence page and insert the Typst macro, either by typing /typst in the editor or by choosing it from the macro browser, where it also answers to searches for "latex", "math", "equation" and "typesetting". Open the macro's configuration panel, paste your Typst source, then save the macro and publish the page. The document compiles and renders when the page is viewed. Each macro holds and renders its own source. To place several documents on one page, add a separate macro for each.
The configuration editor
The configuration panel is a single monospace editor titled Typst source. You paste Typst source into the panel and save to see the rendered result on the page. A size meter tracks how close the source is to the 64 KiB input cap as you type. From an empty editor you can load a maths-heavy sample document, which compiles and renders without edits and gives you a working example to adapt.
What renders
The macro compiles complete Typst documents: headings, prose, lists, tables and code blocks render as they do in Typst itself, and mathematical notation renders in Typst's own maths font. Multi-page documents render as pages stacked vertically down the macro. The rendered output is vector graphics (SVG), so it scales cleanly at any zoom. The text stays selectable, and a reader can highlight it and use the browser's in-page find. Confluence's own page search does not index the Typst source held in the macro configuration. A space search will not find a document by its rendered content.
Fonts
The app bundles Typst's default font families and renders with them: Libertinus Serif for text, New Computer Modern Math for mathematics, and DejaVu Sans Mono for monospaced content. A document that uses these families, which covers Typst's default output, renders as it does locally. Supplying your own fonts is not part of the current version. A document that names a font outside the bundled set still renders, with no warning or error: the compiler substitutes a bundled family in its place (a request for Arial, for example, renders in Libertinus Serif). Output that depends on locally installed fonts will therefore differ from your local render.
Page size and layout
A Typst document usually opens with a #set page(...) rule that fixes its geometry, and when your source includes one the macro renders it unchanged. When the source has no page rule, the macro applies a default in its place (#set page(width: 16cm, height: auto, margin: 1.2em)): the 16cm width fixes the page width inside a Confluence column, and height: auto grows the page to fit its content. Your own #set page always takes precedence. To set the width, height or margins of the output, include the rule you want. Compile-error locations are reported against the source you pasted, so line numbers stay accurate even when the default rule is applied behind the scenes.
Known limitations
The app's security posture keeps all data within your Confluence space, and some limitations follow from it. Where a document runs into one, the macro shows an error message naming what happened.
Page exports (PDF and Word) carry the Typst source, not the rendered output. Confluence's export pipeline cannot run the in-browser compiler, so a page exported to PDF or Word reproduces the macro's Typst source in a code block under the caption "Typst source — rendered on the live page", in place of the typeset result. When a macro has no source configured, the export states that plainly instead of showing an empty code block.
Documents are self-contained. Typst package imports (@preview/…) and file access (image() and #include) are not supported in the current version. Documents render from the source you paste, with no network or file access, and source that uses one of these features is caught before compiling and shown a message naming it.
The app publishes documents you author elsewhere. It has no live preview or editing IDE, and no button to download the render as a PDF or PNG image. Confluence pages are the surface it targets, and Typst authors write in their own tooling.
Source and compile time are capped. Source is limited to 64 KiB and compilation to 10 seconds, each with a message naming the limit reached, which keeps a large or pathological paste from affecting the host page.
Error messages
When the macro cannot render a document, it shows a card on the page explaining why:
- Empty. A macro with no source saved invites you to add some, or to load the maths sample.
- Compile error. Invalid source shows the compiler's own message together with a humanised, 1-based line and column pointing at the source you pasted.
- Unsupported feature. A check before compilation catches a
@preview/package import, animage()call, or#include, and names the specific feature and the version limit. Left to the compiler, these surface as a missing-file or missing-package error. The check reports the feature by name before that happens. It scans the raw source, comments included: a token mentioned in a comment triggers it too. - Timeout. A compile running longer than 10 seconds is stopped and reported as a timeout; the underlying worker is torn down and rebuilt for your next attempt.
- Over the size cap. Source over 64 KiB is stopped before it reaches the compiler, with a message explaining the limit. The cap is enforced in both the configuration editor and the live page, so a document that was valid when saved cannot later blow the limit and break the page.
- Internal error. Anything else that goes wrong falls back to an error card carrying the engine's message.
Each card carries the rendering engine's version in a small footer; quote it if you contact support.
Security and privacy
The Typst compiler runs as WebAssembly inside the macro's own sandboxed iframe, so your documents are compiled in your browser and are never sent to Cloudscript.io or any third party. The app requests no Confluence permissions (scopes: []), declares no external network destinations, and stores nothing outside the macro on your page. The compiler and fonts ship inside the app and load from Atlassian's own infrastructure, so a render makes no request to any non-Atlassian origin.
One narrow exception applies at export. When a page is exported to PDF or Word, a stateless Forge function reads the pasted source from the export payload for the single purpose of writing it into the exported document (see "Known limitations" above). It stores nothing, and logs nothing beyond the structural shape of the payload when the source cannot be found.
Technical note: the macro's iframe declares the unsafe-eval content-security directive, because instantiating the WebAssembly compiler requires it and Forge offers no narrower WASM-only directive. The directive applies only inside the macro's own sandboxed iframe, and it does not permit loading remote code, making network calls, or reaching the host page. The full detail is in the app's Privacy Policy, and our broader approach is described in the Security Policy and Trust Center.
About Typst
Cloudscript Typst Renderer is an independent integration and is not affiliated with, or endorsed by, Typst. Learn more about the language at typst.app.
The app bundles the typst.ts / reflexo-typst WebAssembly toolchain and Typst's default fonts under their respective open-source licences.
Legal
Terms and privacy specific to this app: