# Import Web SDK via CDN

- Human documentation: [https://docs.univer.ai/guides/pdfs/getting-started/installation/cdn](https://docs.univer.ai/guides/pdfs/getting-started/installation/cdn)

- Agent Markdown: [https://docs.univer.ai/guides/pdfs/getting-started/installation/cdn.md](https://docs.univer.ai/guides/pdfs/getting-started/installation/cdn.md)

- Requested language: `en-US`

- Content language: `en-US`

- Documentation version: `1.0.0-rc.0`

- Source: [pdfs/getting-started/installation/cdn.mdx](https://github.com/dream-num/documentation/blob/dev/content/guides/pdfs/getting-started/installation/cdn.mdx)

---

UMD builds expose the following PDF-specific entries. Keep every `@univerjs/*` and `@univerjs-pro/*` URL on the same version.

| UMD path                                        | Global namespace      |
| ----------------------------------------------- | --------------------- |
| `@univerjs-pro/pdfs/lib/umd/index.js`           | `UniverProPdfs`       |
| `@univerjs-pro/pdfs/lib/umd/facade.js`          | `UniverProPdfsFacade` |
| `@univerjs-pro/pdfs-ui/lib/umd/index.js`        | `UniverProPdfsUi`     |
| `@univerjs-pro/pdfs-ui/lib/umd/locale/en-US.js` | `UniverProPdfsUiEnUS` |

Load peer and shared runtime dependencies first, then each package dependency in manifest order. Load `pdfs` before `pdfs-ui`, the UI locale after `pdfs-ui`, and `@univerjs/core/facade` before the PDF Facade entry. UMD does not resolve this dependency graph automatically.

For the package list, CSS imports, plugin registration, and license configuration, return to [Installation & Basic Usage](https://docs.univer.ai/guides/pdfs/getting-started/installation.md).