Add PDF functionality with JavaScript + Vite

Nutrient Web SDK is a JavaScript PDF library for viewing, annotating, and editing PDFs directly in the browser. Use it to add PDF capabilities to any web app.

This guide walks you through the steps to integrate Nutrient Web SDK into your project. By the end, you’ll be able to render a PDF document in the user interface (UI).

Installation

You can load Nutrient Web SDK directly from Nutrient’s content delivery network (CDN). Nutrient maintains the CDN for customers, and it’s our recommended way to get started. For more control and flexibility, use the local installation option.

  1. Add the following <script> tag in your index.html file:

    index.html
    <!doctype html>
    <html lang="en">
    <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Vite App</title>
    </head>
    <body>
    <script src="https://cdn.cloud.pspdfkit.com/pspdfkit-web@1.7.0/nutrient-viewer.js"></script>
    <div id="app"></div>
    <script type="module" src="/main.js"></script>
    </body>
    </html>
  2. You’re now ready to use Nutrient Web SDK and reference window.NutrientViewer in the client-side code.

CSS setup requirements

Nutrient Web SDK requires that the mounting container has an explicit width and height before calling NutrientViewer.load(). The container cannot be 0×0 pixels or the SDK will fail to initialize.

  1. For new Vite projects — Remove conflicting CSS from your style.css file. The default Vite template includes CSS that might interfere with container dimensions:

    /* style.css - Remove these conflicting styles if present */
    body {
    display: flex;
    place-items: center;
    }
  2. Ensure your viewer container has explicit dimensions. The examples in this guide use inline styles (style="height: 100vh; width: 100vw;") which is the recommended approach for most projects.

  3. For existing projects — Check for any CSS framework styles that might interfere with container positioning or dimensions and override them as needed.

Rendering a PDF

  1. Load the PDF file in main.js:

    main.js
    const container = document.getElementById("app");
    // Ensure there’s only one `NutrientViewer` instance.
    window.NutrientViewer.unload(container);
    const { NutrientViewer } = window;
    if (container && NutrientViewer) {
    NutrientViewer.load({
    container,
    // You can also specify a file in the public directory — for example, `/nutrient-web-demo.pdf`.
    document: "https://www.nutrient.io/downloads/nutrient-web-demo.pdf",
    })
    .then((instance) => {
    console.log("Nutrient loaded", instance);
    })
    .catch((error) => {
    console.error(error.message);
    });
    }
  2. Ensure your HTML has the container element:

    index.html
    <!doctype html>
    <html lang="en">
    <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Vite App</title>
    </head>
    <body>
    <script src="https://cdn.cloud.pspdfkit.com/pspdfkit-web@1.7.0/nutrient-viewer.js"></script>
    <div id="app" style="height: 100vh; width: 100vw;"></div>
    <script type="module" src="/main.js"></script>
    </body>
    </html>
  3. Start the development server:

    Terminal window
    npm run dev
  4. You should see the PDF rendered in the Nutrient Web SDK UI.

Next steps

This section outlines additional steps for setting up your project.

TypeScript with the CDN installation

Nutrient Web SDK comes with built-in support for TypeScript. This should work out of the box for local installation. For the CDN installation, follow the steps mentioned in the TypeScript with CDN installation section of the TypeScript guide.

Optimizing the CDN installation

If you use the CDN installation approach in production, Nutrient recommends considering optimizations such as prefetching(opens in a new tab).

Troubleshooting

If you encounter issues, refer to the common issues guide.

Note for developers using AI coding assistants: To get accurate troubleshooting help, copy the content from the troubleshooting guide and include it in your prompt, along with your specific error.