https://www.nutrient.io/guides/web/ Release notes for Nutrient Web SDK Wed, 07 Oct 2026 00:00:00 GMT Wed, 07 Oct 2026 00:00:00 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en-US https://www.nutrient.io/guides/web/release-notes/2024-8/ https://www.nutrient.io/guides/web/release-notes/2024-8/ Thu, 01 Aug 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-7/ https://www.nutrient.io/guides/web/release-notes/2024-7/ Mon, 01 Jul 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-5/ https://www.nutrient.io/guides/web/release-notes/2024-5/ Wed, 01 May 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-4/ https://www.nutrient.io/guides/web/release-notes/2024-4/ Mon, 01 Apr 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-3/ https://www.nutrient.io/guides/web/release-notes/2024-3/ Fri, 01 Mar 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-2/ https://www.nutrient.io/guides/web/release-notes/2024-2/ Thu, 01 Feb 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2024-1/ https://www.nutrient.io/guides/web/release-notes/2024-1/ Mon, 01 Jan 2024 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2023-5/ https://www.nutrient.io/guides/web/release-notes/2023-5/ Mon, 01 May 2023 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2023-4/ https://www.nutrient.io/guides/web/release-notes/2023-4/ Sat, 01 Apr 2023 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2023-3/ https://www.nutrient.io/guides/web/release-notes/2023-3/ Wed, 01 Mar 2023 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2023-2/ https://www.nutrient.io/guides/web/release-notes/2023-2/ Wed, 01 Feb 2023 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2023-1/ https://www.nutrient.io/guides/web/release-notes/2023-1/ Sun, 01 Jan 2023 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2022-5/ https://www.nutrient.io/guides/web/release-notes/2022-5/ Sun, 01 May 2022 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2022-4/ https://www.nutrient.io/guides/web/release-notes/2022-4/ Fri, 01 Apr 2022 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2022-3/ https://www.nutrient.io/guides/web/release-notes/2022-3/ Tue, 01 Mar 2022 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2022-2/ https://www.nutrient.io/guides/web/release-notes/2022-2/ Tue, 01 Feb 2022 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2022-1/ https://www.nutrient.io/guides/web/release-notes/2022-1/ Sat, 01 Jan 2022 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2021-6/ https://www.nutrient.io/guides/web/release-notes/2021-6/ Tue, 01 Jun 2021 00:00:00 GMT { const savedAnnotation = annotations[0]; }); ``` If you used to call `Instance#createAnnotation` to create a widget, and then attached it to a form using `Instance#createFormField`, you’ll now need to create the form field first. You’ll also need to generate and set the widget’s ID using `PSPDFKit#generateInstantId` so that you can reference the widget from the form field before it’s added to the document. Here’s an example of how you can do this using the new `Instance.html#create` API: ```js const annotation = new NutrientViewer.Annotations.WidgetAnnotation({ id: NutrientViewer.generateInstantId(), pageIndex: 0, formFieldName: "name", boundingBox: new NutrientViewer.Geometry.Rect({ left: 10, top: 20, width: 60, height: 40 }) }); const form = new NutrientViewer.FormFields.TextFormField({ name: "name", annotationIds: NutrientViewer.Immutable.List([annotation.id]), label: "A label" }); instance.create([annotation, form]); ``` By default, this makes signatures respect their aspect ratio when being resized by their corner handles. To opt out of this and go back to the old behavior, you can use the new `onAnnotationResizeStart` callback option: ```js NutrientViewer.load({ onAnnotationResizeStart: (event) => { if (event.annotation.isSignature && !event.isShiftPressed) { return { maintainAspectRatio: false }; } return undefined; } }); ``` For a full list of changes, check out the changelog. Learn about the API changes and migration steps for PSPDFKit for Web 2021.6, including updates to annotation, bookmark, and form field methods.]]> https://www.nutrient.io/guides/web/release-notes/2021-5/ https://www.nutrient.io/guides/web/release-notes/2021-5/ Sat, 01 May 2021 00:00:00 GMT !isIE11 && !isOldSafari }); ``` For a full list of changes, check out the changelog. Explore the new AP stream rendering in PSPDFKit 2021.5 and understand important migration steps for improved performance in older browsers.]]> https://www.nutrient.io/guides/web/release-notes/2021-4/ https://www.nutrient.io/guides/web/release-notes/2021-4/ Thu, 01 Apr 2021 00:00:00 GMT ; ``` Some of the frequently used types are: ```js type Instance = InstanceType; type Rect = InstanceType; type Color = InstanceType; type Annotation = InstanceType; type TextSelection = InstanceType; type ToolbarItems = InstanceType["toolbarItems"]; type List = ReturnType; type Awaited = T extends PromiseLike ? Awaited : T; type AnnotationsList = Awaited>; ``` We’re exploring ways to make this experience better in our upcoming releases. For a full list of changes, check out the changelog. Explore the new features of PSPDFKit 2021.4, including default JavaScript actions and improved TypeScript declarations for better integration and accuracy.]]> https://www.nutrient.io/guides/web/release-notes/2021-3/ https://www.nutrient.io/guides/web/release-notes/2021-3/ Mon, 01 Mar 2021 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2021-2/ https://www.nutrient.io/guides/web/release-notes/2021-2/ Mon, 01 Feb 2021 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2021-1/ https://www.nutrient.io/guides/web/release-notes/2021-1/ Fri, 01 Jan 2021 00:00:00 GMT { return it.type !== "export-pdf"; }); NutrientViewer.load({ ...configuration, toolbarItems }); ``` - (#25309) This release slightly changes the behavior of specifying a range of pages to search within when using the `NutrientViewer.Instance#search()` API. Previously, specifying both `startPageIndex` and `endPageIndex` made search results include matches from the start page index up until the end page index, without including those from the last page. Now, search results also include those from the end page index that’s specified. To keep the previous behavior, you’ll instead need to call `NutrientViewer.Instance#search`, passing `endPageIndex - 1` as the `endPageIndex` property value. - (#27856) You’ll no longer be allowed to change the `rootId` of a comment once it has been created. If you were updating the `rootId` before, make sure you create a new comment instead. - (#27443) This release prevents setting `NutrientViewer.ViewState#interactionMode` to a value that enables annotation creation with the UI when in read-only mode (`NutrientViewer.ViewState#readOnly` is `true`). The new interaction mode set via `Instance#setViewState` is set as `null` in this case, and a warning is emitted to the console. If you use PSPDFKit Server, make sure you read the 2021.1 server migration guide. For a full list of changes, check out the changelog. [pspdfkit for web 2021.1]: /blog/pspdfkit-web-2021-1-collaboration-permissions/ [mdn page]: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API [mozilla bug]: https://bugzilla.mozilla.org/show_bug.cgi?id=1469395 [wasm issue]: https://github.com/WebAssembly/spec/issues/821 [`nutrientviewer.instance#search()`]: /api/web/classes/NutrientViewer.Instance.html#search [2021.1 server migration guide]: /guides/product-archives-and-deprecated-solutions/ [changelog]: /guides/web/changelog/#2021.1 [web sdk 2020.6 release notes]: /guides/web/release-notes/2020-6/ Navigate changes in PSPDFKit for Web 2021.1 and optimize your configuration for new features like the Export PDF button. Update your migration strategy now!]]> https://www.nutrient.io/guides/web/release-notes/2020-6/ https://www.nutrient.io/guides/web/release-notes/2020-6/ Mon, 01 Jun 2020 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2020-5/ https://www.nutrient.io/guides/web/release-notes/2020-5/ Fri, 01 May 2020 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2020-4/ https://www.nutrient.io/guides/web/release-notes/2020-4/ Wed, 01 Apr 2020 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2020-3/ https://www.nutrient.io/guides/web/release-notes/2020-3/ Sun, 01 Mar 2020 00:00:00 GMT { instance.setViewState(s => s.set("interactionMode", NutrientViewer.InteractionMode.INK_SIGNATURE) ); }); ``` If you use PSPDFKit Server, make sure you read the 2020.3 migration guide. For a full list of changes, check out the changelog. [pspdfkit for web 2020.3]: /blog/pspdfkit-adds-redaction-and-improved-digital-signatures-to-web/ [changelog]: /guides/web/changelog/#2020.3 [2020.3 migration guide]: /guides/product-archives-and-deprecated-solutions/ [web sdk 2020.2 release notes]: /guides/web/release-notes/2020-2/ Explore the PSPDFKit Web 2020.3 migration guide with key updates and changes for a smooth integration experience.]]> https://www.nutrient.io/guides/web/release-notes/2020-2/ https://www.nutrient.io/guides/web/release-notes/2020-2/ Sat, 01 Feb 2020 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2020-1/ https://www.nutrient.io/guides/web/release-notes/2020-1/ Wed, 01 Jan 2020 00:00:00 GMT { instance.getFormFields().then(formFields => { const formField = formFields.find( formField => formField.name === event.annotation.formFieldName ); console.log(formField); }); }); ``` If you are using `event.formField`, here is the change you need to make: **Before** ```javascript instance.addEventListener("annotations.focus", event => { console.log(event.formField); }); instance.addEventListener("annotations.blur", event => { console.log(event.formField); }); ``` **After** ```javascript instance.addEventListener("annotations.focus", event => { instance.getFormFields().then(formFields => { const formField = formFields.find( formField => formField.name === event.annotation.formFieldName ); console.log(formField); }); }); instance.addEventListener("annotations.blur", event => { instance.getFormFields().then(formFields => { const formField = formFields.find( formField => formField.name === event.annotation.formFieldName ); console.log(formField); }); }); ``` - When the Digital Signatures component is included in the license, `NutrientViewer.Instance#exportPDF` will export signed documents as incrementally saved by default so as to prevent modifying signed data, which would invalidate the document’s digital signatures. However, setting the `incremental` flag to `false` will override this behavior. If the Digital Signatures component is not included in the license, the former behavior will be followed and signed documents will be exported as fully saved by default. In order to prevent signed data corruption in this case, the `incremental` flag should be explicitly set: ```js instance.exportPDF({ incremental: true }); ``` - Previously, the object returned by `NutrientViewer.ViewState#viewportPadding` had the `vertical` value under the `horizontal` property and vice versa. This has been now fixed. If you were relying on the previous returned value, you will need to adjust your implementation accordingly. - The order in which annotations are rendered has been modified. In previous versions, annotations of the same type would be rendered in the same layer, in the following order from back to front: - Text markup - Link - Text - Widget - Stamp - Image - Ink - Shape - Note Beginning with the current release, annotations will be rendered in the same order they are in the document, regardless of their type. New annotations will always be rendered on top of the last one that has been added. If your implementation relies on the former annotation rendering order, you may need to rearrange the order in which annotations are created so as to continue obtaining the same result. You would need to first create the annotations that you want to be rendered in the background, followed by the ones that you want to be rendered in the foreground. For example: First create text annotations, then stamp annotations, then ink and shape annotations, in that order. This way, your annotations will keep rendering in the order they had with the former behavior. If your annotations never overlap, this change will probably not affect your implementation at all. - The note annotation icon in the main toolbar has been updated. If you use PSPDFKit Server, make sure you read the 2020.1 migration guide. For a full list of changes, check out the changelog. [pspdfkit for web 2020.1]: /blog/pspdfkit-web-2020-1/ [`nutrientviewer.annotations.rectangleannotation#cloudyborderinsetrect`]: /api/web/classes/NutrientViewer.Annotations.RectangleAnnotation.html#cloudyborderinsetrect [`nutrientviewer.annotations.rectangleannotation#cloudyborderinset`]: /api/web/classes/NutrientViewer.Annotations.RectangleAnnotation.html#cloudyborderinset [`nutrientviewer.annotations.ellipseannotation#cloudyborderinsetrect`]: /api/web/classes/NutrientViewer.Annotations.EllipseAnnotation.html#cloudyborderinsetrect [`nutrientviewer.annotations.ellipseannotation#cloudyborderinset`]: /api/web/classes/NutrientViewer.Annotations.EllipseAnnotation.html#cloudyborderinset [`nutrientviewer.geometry.inset`]: /api/web/classes/NutrientViewer.Geometry.Inset.html [`nutrientviewer.geometry.rect`]: /api/web/classes/NutrientViewer.Geometry.Rect.html [`nutrientviewer.geometry.inset#fromvalue`]: /api/web/classes/NutrientViewer.Geometry.Inset.html#fromvalue [`nutrientviewer.instance#exportpdf`]: /api/web/classes/NutrientViewer.Instance.html#exportpdf [`nutrientviewer.viewstate#viewportpadding`]: /api/web/classes/NutrientViewer.ViewState.html#viewportpadding [changelog]: /guides/web/changelog/#2020.1 [2020.1 migration guide]: /guides/product-archives-and-deprecated-solutions/ [react intl]: https://github.com/formatjs/react-intl [standard `intl` web api]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl [web sdk 2019.5 release notes]: /guides/web/release-notes/2019-5/ Explore the significant updates in PSPDFKit Web 2020.1, including localization changes and deprecated features for seamless migration.]]> https://www.nutrient.io/guides/web/release-notes/2019-5/ https://www.nutrient.io/guides/web/release-notes/2019-5/ Wed, 01 May 2019 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2019-4/ https://www.nutrient.io/guides/web/release-notes/2019-4/ Mon, 01 Apr 2019 00:00:00 GMT -*.js` files are used for internationalization files, e.g. `pspdfkit-lib/chunk-locale-de-*.js` for the German localization. - `chunk-standalone-*.js` is for all Standalone-specific artifacts. - `chunk-server-*.js` is for all Server-specific artifacts. Note that the last part of the file name is still a hash of its content. This ensures we don’t run into caching issues when artifacts are updated. - The icons in the toolbar were changed in order to shrink the toolbar height. Additionally, the icon size changed from 18x18 px to 24x24 px. - The WebAssembly and asm.js artifacts now have a content hash as part of the file name. This allows you to configure a long-term caching strategy and make use of advanced features like WASM code caching. The affected files are: - `pspdfkit-lib/pspdfkit.wasm` ➡️ `pspdfkit-lib/pspdfkit-.wasm` - `pspdfkit-lib/pspdfkit.wasm.js` ➡️ `pspdfkit-lib/pspdfkit-.wasm.js` - `pspdfkit-lib/pspdfkit.asm.js` ➡️ `pspdfkit-lib/pspdfkit-.asm.js` - `pspdfkit-lib/pspdfkit.asm.js.mem` ➡️ `pspdfkit-lib/pspdfkit-.asm.js.mem` - The thumbnail sidebar now comes with a changed layout. All public CSS classes can still be used to customize the styling: - `.PSPDFKit-Sidebar-Thumbnails-Page` - `.PSPDFKit-Sidebar-Thumbnails-Page-Image` - `.PSPDFKit-Sidebar-Thumbnails-Page-Label` - `.PSPDFKit-Sidebar-Thumbnails-Page-Selected` If you use PSPDFKit Server, make sure you read the 2019.4 server migration guide. For a full list of changes, check out the changelog. [pspdfkit for web 2019.4]: /blog/pspdfkit-web-2019-4/ [wasm code caching]: https://v8.dev/blog/wasm-code-caching [changelog]: /guides/web/changelog/#2019.4 [2019.4 server migration guide]: /guides/product-archives-and-deprecated-solutions/ [`nutrientviewer.defaulttoolbaritems`]: /api/web/variables/NutrientViewer.defaultToolbarItems.html [`nutrientviewer.configuration#theme`]: /api/web/interfaces/Configuration.html#theme [web sdk 2019.3 release notes]: /guides/web/release-notes/2019-3/ Explore key enhancements in PSPDFKit for Web 2019.4, including UI changes, a new Document Editor, and migration tips for seamless adaptation.]]> https://www.nutrient.io/guides/web/release-notes/2019-3/ https://www.nutrient.io/guides/web/release-notes/2019-3/ Fri, 01 Mar 2019 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2019-2/ https://www.nutrient.io/guides/web/release-notes/2019-2/ Fri, 01 Feb 2019 00:00:00 GMT ` tag and want to maintain its current position, you could: - Query the current position in `onDisappear` and apply it again with `onAppear`, or - Move (`appendChild`) the ` https://www.nutrient.io/guides/web/release-notes/2019-1/ https://www.nutrient.io/guides/web/release-notes/2019-1/ Tue, 01 Jan 2019 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-7/ https://www.nutrient.io/guides/web/release-notes/2018-7/ Sun, 01 Jul 2018 00:00:00 GMT .PSPDFKit-Toolbar-Button`. - We added a `rotation` property to annotations. This change shouldn’t affect current annotations. However, when using Server deployment, some documents might need to be uploaded again if the rotation is off. For a full list of changes, check out the changelog. [pspdfkit for web 2018.7]: /blog/pspdfkit-web-2018-7/ [changelog]: /guides/web/changelog/#2018.7 [2018.7 server migration guide]: /guides/product-archives-and-deprecated-solutions/ [web sdk 2018.6 release notes]: /guides/web/release-notes/2018-6/ Learn about customizable tooltips, enhanced DOM support, and other important features in PSPDFKit for Web 2018.7.]]> https://www.nutrient.io/guides/web/release-notes/2018-6/ https://www.nutrient.io/guides/web/release-notes/2018-6/ Fri, 01 Jun 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-5/ https://www.nutrient.io/guides/web/release-notes/2018-5/ Tue, 01 May 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-4/ https://www.nutrient.io/guides/web/release-notes/2018-4/ Sun, 01 Apr 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-3/ https://www.nutrient.io/guides/web/release-notes/2018-3/ Thu, 01 Mar 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-2/ https://www.nutrient.io/guides/web/release-notes/2018-2/ Thu, 01 Feb 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2018-1/ https://www.nutrient.io/guides/web/release-notes/2018-1/ Mon, 01 Jan 2018 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2017-9/ https://www.nutrient.io/guides/web/release-notes/2017-9/ Fri, 01 Sep 2017 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2017-8/ https://www.nutrient.io/guides/web/release-notes/2017-8/ Tue, 01 Aug 2017 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2017-7/ https://www.nutrient.io/guides/web/release-notes/2017-7/ Sat, 01 Jul 2017 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2017-6/ https://www.nutrient.io/guides/web/release-notes/2017-6/ Thu, 01 Jun 2017 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/2017-3/ https://www.nutrient.io/guides/web/release-notes/2017-3/ Wed, 01 Mar 2017 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-22/ https://www.nutrient.io/guides/web/release-notes/1-22/ Wed, 07 Oct 2026 00:00:00 GMT ({ content: myCustomSearch(props), }), }, }, }); // Use the equivalent slot instead. NutrientViewer.load({ ui: { search: (getInstance, id) => ({ render: () => myCustomSearch(), }), }, }); ``` Four exports were part of that API and now throw a migration error when accessed, rather than being `undefined`: `NutrientViewer.UI.createBlock`, `NutrientViewer.UI.Recipes`, `NutrientViewer.UI.Decorators`, and `NutrientViewer.UI.Interfaces`. The rendered DOM is unchanged — every `data-block-id` attribute is preserved — so visual tests and selectors that target them keep working. For the list of slots and what each one replaces, refer to the UI customization and supported slots guides. ### Deprecated collection methods The SDK’s collection types inherit Immutable’s full method surface, most of which the SDK has never supported. Nineteen of those methods are now marked deprecated in the published type declarations and the API reference, each naming the supported replacement. **No method was removed and every call keeps working**, but the editor now flags them before you build on something that can’t be kept. | Method | Replacement | | -------------- | ----------------------------------------------------------------------------------- | | `asImmutable` | Build the value once, or use `withMutations()`. | | `asMutable` | Use `withMutations()`. | | `cacheResult` | Drop the call — the collections the SDK exposes are already eager. | | `entrySeq` | Use `entries()`. | | `filterNot` | Use `filter()` with the predicate negated. | | `findEntry` | Use `entries()`, taking the entry you need. | | `findKey` | Loop over `entries()`. | | `flatten` | Use `flatMap()`. | | `fromEntrySeq` | Use `Map(entries)`. | | `hasIn` | Use `get()` followed by `has()`. | | `mergeIn` | Use `update()` followed by `merge()`. | | `removeIn` | Use `deleteIn()`, or `update()` followed by `delete()`. | | `setSize` | Construct the collection with the values it should hold. | | `toIndexedSeq` | Use `values()`. | | `toKeyedSeq` | Use `entries()`. | | `toMap` | Use `Map(entries())`. | | `toSeq` | Use `entries()` on a keyed collection, or `values()` on an indexed or set-like one. | | `toSetSeq` | Use `values()`. | | `wasAltered` | Compare the collections with `equals()`. | ### Compound measurements Measurement labels can show a mixed-unit value — “6 ft 3 in” instead of “6.25 ft” — matching the format Acrobat and Bluebeam Revu author. Compound units are configured per scale, as an ordered list of progressively smaller units, each with its own precision, appended to the scale’s primary unit: ```js NutrientViewer.load({ measurementValueConfiguration: (documentScales) => [ { name: "Feet & Inches", scale: { unitFrom: NutrientViewer.MeasurementScaleUnitFrom.INCHES, unitTo: NutrientViewer.MeasurementScaleUnitTo.FEET, fromValue: 1, toValue: 3 }, precision: NutrientViewer.MeasurementPrecision.TWO, compoundUnits: [ { unitTo: NutrientViewer.MeasurementScaleUnitTo.INCHES, precision: NutrientViewer.MeasurementPrecision.WHOLE } ], selected: true }, ...documentScales ] }); ``` The chain is generic across measurement systems — `ft → in`, `m → cm → mm`, `yd → ft → in` — and each annotation renders from its own scale, so a metric scale can’t pick up an imperial sub-unit. A configured sub-unit that isn’t strictly smaller than the scale’s unit falls back to a single-unit label, as do area measurements. The chain is persisted on the annotation as a multi-entry `/Measure /D` number-format array, so it survives save, reload, and export, and compound measurements authored elsewhere are read back correctly. `instance.setMeasurementScale(scale, { compoundUnits, name })` writes the scale and its chain into the document, so the scale is offered again after reopening without re-supplying `measurementValueConfiguration`. Compound measurements are standalone mode only. Document Engine ignores the compound chain. For more information, refer to the measurements guide. ### Per-page initial render callback `onInitialPageRender` is called once per page, the first time that page renders, which makes time to first rendered page directly measurable instead of something you infer from timers or mutation observers: ```js const startedAt = performance.now(); let reported = false; NutrientViewer.load({ onInitialPageRender: function ({ pageIndex }) { if (reported) return; reported = true; console.log(`page ${pageIndex} rendered after ${performance.now() - startedAt}ms`); }, // ... }); ``` The callback fires only on a successful render, so the page already has content drawn when you’re called. It never fires twice for the same page index — zoom, rotation, resize, and scrolling back to a page don’t re-trigger it — and the first call can arrive before `load()` resolves. Pages next to the current one are pre-rendered, so a page can be reported slightly before the reader scrolls to it. The `OnInitialPageRenderCallback` and `InitialPageRenderInfo` types ship in the public declarations. ### Typed message IDs and locale tags Localization is now typed. Every message ID the SDK ships and every locale it provides a catalog for is suggested as you type, and the types admit that a locale you haven’t loaded yet isn’t there: ```ts NutrientViewer.I18n.messages.en = { print: "Print document" }; await NutrientViewer.I18n.preloadLocalizationData("de"); NutrientViewer.I18n.messages.de!.print = "Dokument drucken"; await instance.setLocale("de"); ``` `locale`, `setLocale()`, `preloadLocalizationData()`, and `loadTextComparison()` autocomplete the shipped locale tags while still accepting a custom tag you push onto `NutrientViewer.I18n.locales`. The `Locale`, `MessageId`, `LocaleMessages`, and `LocaleMessageOverrides` types are part of the public API. **This is a type-only tightening**: the locale keys of `NutrientViewer.I18n.messages` are now optional, so reading `NutrientViewer.I18n.messages.de.print` no longer compiles. Add a guard, or a non-null assertion after preloading. Runtime behavior is unchanged, and JavaScript integrations are unaffected. For the full list of message IDs, refer to the localization guide in the API reference. ### `setFocus()` in PDF JavaScript Form fields support the `setFocus()` PDF JavaScript method, so a document script can move the cursor into a named field: ```js this.getField("total").value = "0"; this.getField("total").setFocus(); ``` The call previously threw, which discarded the rest of the script — including assignments it had already made. A field on another page is scrolled into view rather than only scrolled to the top of its page. ### Immediate saving for DWS Viewer API sessions A DWS Viewer API session loaded with `NutrientViewer.load({ container, session })` runs Instant, but was using the save mode meant for Instant being off. It now uses `AutoSaveMode.IMMEDIATE`, the mode Instant implies. **Edits are sent as they’re made instead of being batched to the next flush point**, `hasUnsavedChanges()` reports accurately, and applying redactions completes instead of hanging indefinitely. Passing `instant: false` or an explicit `autoSaveMode` is unaffected. ### Other additions - `NutrientViewer.Error` ships type declarations instead of being typed as `any`. - The `inlineWorkers` configuration option moved from `StandaloneConfiguration` to `SharedConfiguration`, so server-backed deployments can opt out of inline workers as well. - Importing Instant JSON that contains many form field values on JavaScript-backed forms is faster: the document’s calculations run once for the whole import instead of once per value. - GdPicture is updated to 14.4.8.1. Refer to the GdPicture changelog for details. - The GdPicture WASM components are listed in the Web SDK SBOM. - The internal static `defaultValues` property is no longer part of the published type declarations. ### Rendering - Fixes annotation and form field text being dropped when it contains symbols such as ★ (U+2605) that were erroneously classified as emojis. - Fixes emoji missing from annotation text when using dynamically loaded fonts. - Fixes incorrect font styles for diacritic characters in PDFs that use configured font substitutions. - Fixes applying a redaction removing unrelated text on the same page in more cases, including text drawn by a form XObject, an annotation appearance, a soft mask, or a Type 3 glyph. - Fixes applying a redaction removing unrelated text on the same page when that text is drawn with the `'` or `"` operators. ### Forms and document editing - Fixes a PDF JavaScript call to `checkThisBox` being ignored on a read-only checkbox or radio button. - Fixes a text form field showing its previously typed value again when refocused after a PDF JavaScript action changed it. - Fixes calculated form fields keeping a stale value, and reporting a self-modification error, when their stored values are imported through Instant JSON or XFDF. - Fixes a crash when processing or exporting large documents whose forms use a calculation order. - Fixes copied form fields not being fillable on the pages where they appear in some documents. - Fixes form field text rendering as unrelated symbols when the requested font is missing from the document. - Fixes symbols like checkmarks being replaced by fallback glyphs in exported and flattened form field appearances when dynamic fonts are enabled. - Fixes `WidgetAnnotation#isBold` and `isItalic` deserializing as `null` instead of the documented `false` default when the document specifies no font style. - Fixes non-image payloads being embedded into populated Office document templates. Payloads without a supported image signature, or whose explicit format conflicts with detected image data, are now rejected. ### User interface and accessibility - Fixes Command/Control-drag failing to create an annotation selection rectangle on pages after the first. - Fixes a font size, font family, text color, or background color change applied to a plain text annotation with `instance.update()` not appearing in the open inline editor until the editing session ends. - Fixes an error shown in the sidebar when `ViewState#sidebarOptions` omits the entry for that sidebar. - Fixes an uncatchable “Content editing not initialized” promise rejection when the content editor is used while a content editing session is being saved. - Fixes annotation tools becoming usable when read-only mode is disabled on a license without annotation editing. - Fixes misaligned comments and clipped comment edit fields when a custom `CommentAvatar` renderer is used. - Fixes content editor errors omitting the underlying cause from their message. - Fixes unrelated errors being reported as an invalid theme with their original message rewritten. ### Loading, platform, and API reference - Fixes scrolling through text-heavy documents temporarily blocking interaction with the viewer and the embedding application, by moving synthetic text-selection font serialization to a dedicated worker. Deployments with a strict Content Security Policy should review the `inlineWorkers` configuration option. - Fixes broken links and missing type descriptions in the API reference. - Fixes the API reference showing an internal type for the `instant` configuration option. - Fixes the API reference showing rest parameters as a single array argument instead of `...name`. - Fixes the `getBlocks` API reference claiming it reads all blocks, and documents that a page reads empty until its text is detected. - Fixes the documented return value of `setDocumentComparisonMode()`, which described only one of the three outcomes the returned promise can represent. For a full list of fixes, refer to the changelog. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. In server-backed mode, using `SearchType.WORD_BASED`, removing password protection during PDF export, and removing annotation notes after an XFDF roundtrip require Document Engine 1.16.0 or later. Document-defined annotation tab order, `Annotation.createdBy`, `overprintPreview`, and `blackRendering` require Document Engine 1.18.0 or later. Compound measurements are standalone mode only and are ignored by Document Engine. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.21 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.22.0 [web sdk 1.21 release notes]: /guides/web/release-notes/1-21/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [ui-customization]: /guides/web/user-interface/ui-customization/introduction/ [supported-slots]: /guides/web/user-interface/ui-customization/supported-slots/ [measurements]: /guides/web/measurements/configure-measurements/ [localization-api]: /api/web/documents/Localization.html [csp]: /guides/web/troubleshooting/content-security-policy/ [gdpicture-changelog]: /guides/dotnet/changelog/#14.4.8.1 Lists important changes for Nutrient Web SDK 1.22]]> https://www.nutrient.io/guides/web/release-notes/1-21/ https://www.nutrient.io/guides/web/release-notes/1-21/ Wed, 07 Oct 2026 00:00:00 GMT { console.log(annotation.createdBy); }); ``` Both properties are read-only and assigned by the backend — a locally set value is never sent. They’re available on server-backed deployments only, and are `null` for records created without an authenticated user, or when the server holds an author it can no longer resolve to an upstream user ID. `Annotation.createdBy` requires Instant synchronization against Document Engine 1.18.0 or later. ### Print-production rendering Two configuration options control rendering fidelity for prepress and soft-proofing workflows. Documents that don’t use CMYK color or overprinting are unaffected by either option. ```js NutrientViewer.load({ overprintPreview: NutrientViewer.OverprintPreview.OFF, blackRendering: NutrientViewer.BlackRendering.PURE_BLACK, // ... }); ``` - `overprintPreview` controls whether the renderer simulates the overprinting a document uses, where overlapping inks print on top of each other instead of knocking each other out. It defaults to `AUTO`, which simulates overprinting when the document uses it; `OFF` disables the simulation. - `blackRendering` controls how exact 100 percent K-only CMYK black is rendered. It defaults to `ACCURATE`, which renders it as the dark charcoal Acrobat shows on screen; `PURE_BLACK` maps it to `#000000` instead, which some print workflows prefer for checking black-only content. In server-backed mode, both options require Document Engine 1.18.0 or later and are ignored by older servers. ### Terminal page render failures A page render that exhausts WebAssembly memory is retried once. When the retry also fails, the SDK now displays a localized page-level error and emits `page.renderError`, so your application can react instead of leaving the user with a blank page: ```js instance.addEventListener("page.renderError", (event) => { if (event.error instanceof NutrientViewer.OutOfMemoryError) { console.log(event.pageIndex, event.pageStillDisplaysContent); } }); ``` `pageStillDisplaysContent` reports whether the page is still showing earlier, lower-resolution content when the event is emitted. The device itself can still have free memory — the failure is specific to the WebAssembly heap. ### XLSX and PPTX template population `populateDocumentTemplate()` now accepts XLSX and PPTX templates in addition to DOCX, and it returns the populated file as an `ArrayBuffer`. XLSX templates process every worksheet and support placeholders, conditions, row loops, images, and typed number, date, percentage, and Boolean cells. Column loops and list expansion within a single cell aren’t supported, and formula references, structured table ranges, and defined names aren’t adjusted when row loops insert rows. PPTX templates support placeholders, loops, conditions, tables, and images on slides; slide masters, slide layouts, and speaker notes aren’t processed. ### Other additions - The API reference ships a localization guide listing the locales the SDK provides catalogs for and every overridable message ID. - `setLocale()` and `preloadLocalizationData()` throw a clearer error when a locale can’t be loaded and expose the underlying failure as `error.cause`. - AI Assistant agent skills now require a `description`, which the agent uses to decide when to apply each skill. - Dark-color fidelity of Multiply and related blend modes in CMYK transparency groups is improved by blending in the group’s color space. ### Rendering - Fixes non-isolated transparency groups compositing their backdrop twice, which rendered blended content too dark or washed out. - Fixes shaded boxes appearing over artwork when rendering PDFs with DeviceN black gradients in CMYK transparency groups. - Fixes missing page content when rendering PDFs with certain inline images. - Fixes missing CJK text and incorrect Yen symbols in PDFs that use configured font substitutions. - Fixes the black box of an applied redaction being misplaced and incorrectly sized when the redacted content sits inside a transformed form XObject. - Fixes layer visibility changes through `setLayersVisibilityState()` or the layers sidebar hiding content in optional content groups that `getLayers()` doesn’t expose, such as page-level OCGs in CAD documents. These groups now keep the document’s native visibility. - Fixes slow saving of free text annotations containing emojis. ### Forms and document editing - Fixes text form fields rejecting all input when their JavaScript Keystroke script calls `AFMergeChange` or `AFExtractNums`. - Fixes editing a radio button option in Form Creator moving the group’s option values onto the wrong widgets when the document was exported. - Fixes `applyRedactions()` being skipped when batched with page move or removal operations. - Fixes keyboard page reordering in the Document Editor losing its drop position when the interface updates mid-drag. ### Collaboration - Fixes a comment edit being silently dropped when it was made in the brief window between the comment’s create request being sent and the server’s acceptance of it. - Fixes an unsaved comment draft carrying over into another comment thread when switching between threads. ### User interface and accessibility - Fixes the measurement scale target unit picker announcing the source unit picker’s label to screen readers. - Fixes Japanese and Korean UI strings that displayed stray characters instead of a value, dropped the unit after a point size, or reversed the two numbers in “N of M” counters such as the search result position. - Fixes translations in Czech, Slovak, and Dutch that rendered a raw placeholder or failed to render, affecting the comment count, the comment thread label, and the duplicate form field name error. ### Loading, platform, and API reference - Fixes a Content Security Policy violation reported on every load when using the recommended `script-src 'self' 'wasm-unsafe-eval'` policy. - Fixes the import of annotation and action JSON whose numeric fields aren’t finite numbers, which previously produced annotations that render incorrectly. - Fixes the missing `Serializers.BookmarkJSON` properties in the API reference. For a full list of fixes, refer to the changelog. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. In server-backed mode, using `SearchType.WORD_BASED`, removing password protection during PDF export, and removing annotation notes after an XFDF roundtrip require Document Engine 1.16.0 or later. Document-defined annotation tab order, `Annotation.createdBy`, `overprintPreview`, and `blackRendering` require Document Engine 1.18.0 or later. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.20 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.21.0 [web sdk 1.20 release notes]: /guides/web/release-notes/1-20/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [localization-api]: /api/web/documents/Localization.html Lists important changes for Nutrient Web SDK 1.21]]> https://www.nutrient.io/guides/web/release-notes/1-20/ https://www.nutrient.io/guides/web/release-notes/1-20/ Wed, 07 Oct 2026 00:00:00 GMT ({ content: myCustomSearch(props), }), }, }, }); // Use the equivalent slot instead. NutrientViewer.load({ ui: { search: (getInstance, id) => ({ render: () => myCustomSearch(), }), }, }); ``` Because `_blocks` isn’t part of the published type declarations, the console is the only channel available for this notice. Loading a configuration that uses it now logs one deprecation warning: - Configuring the same component through both APIs logs an additional warning per component, naming the slot path and the block so you know exactly what to migrate. Which of the two renders depends on the component and on what the slot provides, so this case was previously invisible. The `minimal` UI preset hides every slot a block maps onto, so conflicts surface there too. - Passing `_blocks` to `instance.setUI()` has never had an effect — the value is always overwritten with the current one — and now reports that instead of failing silently. For the list of slots and what each one replaces, refer to the UI customization and supported slots guides. ### Default parameter values in PDF JavaScript PDF JavaScript function declarations now support default parameter values, so documents whose scripts rely on them evaluate correctly instead of failing to parse: ```js function formatTotal(amount, currency = "USD") { return amount + " " + currency; } ``` For more information, refer to the JavaScript support guide. ### Stricter validation for models, toolbars, and tool items Model, toolbar, and tool item validation now runs on shared schemas rather than hand-written checks, which closes a set of holes where malformed input was accepted or surfaced as an opaque `TypeError`. **Input that was previously tolerated now throws**, so review any call site that passes values built from user input or an external source. - Non-finite numbers (`NaN`, `Infinity`, `-Infinity`) are rejected where a number is expected — for example, `Bookmark.sortKey` and `CustomOverlayItem.pageIndex`. - Malformed comments, mentionable users, and document descriptors report a named validation error. For example, `new NutrientViewer.DocumentDescriptor(null)` now throws `DocumentDescriptor: Expected an object.` instead of `TypeError: Cannot destructure property 'filePath' of 'null'`. - `instance.setMentionableUsers()` stored its argument unchecked and now applies the same rules as the `load()` configuration path. - `avatarUrl` and `description` on mentionable users are checked whenever they’re present, not only when they’re truthy, so values such as `0` and `false` are no longer accepted. - Toolbar items, tool items, Document Editor footer items, and inline text selection toolbar items reject invalid `string` and `mediaQueries` values consistently across all variants. - DOM nodes in tool items are validated by node type rather than with `instanceof Node`, so a node created in another realm — an iframe, for example — is accepted. For any given invalid input, the field reported first is unchanged, so error strings you match on in existing code stay the same. ### Read-only geometry model types The geometry models — `Rect`, `Point`, `Size`, `Inset`, `DrawingPoint`, and `TransformationMatrix` — now expose read-only properties and the same standard Immutable Record method subset as every other model. This is a type-only change: Runtime behavior is untouched, and these objects were already immutable. **TypeScript now reports an error where your code assigns to a property**; use `set()` to derive a new value instead: ```js const rect = new NutrientViewer.Geometry.Rect({ left: 0, top: 0, width: 100, height: 50, }); // Previously allowed by the types, but never applied at runtime. // rect.left = 10; // Derive a new value instead. const movedRect = rect.set("left", 10); ``` ### Secondary toolbar no longer covers document content The secondary toolbar reserves scrollable space while it’s open instead of overlaying the document, so content underneath it is always reachable. The space is reserved above the first page with the default toolbar placement, and below the last page when `toolbarPlacement` is `BOTTOM`. ### Performance improvements - Content Editor startup is faster because fonts are cached and reused across editing sessions instead of being loaded again for each one. - The thumbnails sidebar feels immediate while being resized: Thumbnails settle directly at their final position rather than animating into it, so the list no longer shifts after it renders and click targets stay steady. ### Other additions - GdPicture is updated to 14.4.7. Refer to the GdPicture changelog for details. - Progressive page renders that exhaust WebAssembly memory now surface a typed out-of-memory error instead of retrying through direct rendering, which prevents memory-exhaustion crash loops on very large pages. ### Collaboration and forms - Fixes updates to annotations, comments, and form fields being silently discarded when Collaboration Permissions are enabled and the update was issued before Document Engine acknowledged the record’s creation. - Fixes chained form field calculations not being fully recalculated when the document’s calculation order lists dependent fields before the fields they depend on. - Fixes Document Compare requiring a trailing slash on the AI Assistant `backendUrl`. ### Rendering and editing - Fixes washed-out colors when rendering PDFs that use CMYK transparency groups with process black or DeviceN shadings. - Fixes dashed lines with fractional dash patterns rendering as solid lines. - Fixes free text callout annotations sometimes rendering text too small or clipped. - Fixes ink strokes changing after they’re completed. - Fixes a crash on Safari and iOS 15.4–16 when rendering text containing a URL. ### User interface - Fixes the viewer losing its scroll position when opening or closing the sidebar, which left it showing a blank page or jumping to the first page instead of staying on the current page. - Fixes annotation placement when browser extensions load with custom toolbars. - Fixes the loading skeleton showing its toolbar at the top when `toolbarPlacement` is set to `BOTTOM`. - Fixes the text annotation opacity slider on mobile closing after a single step instead of following a press and drag to the chosen value. - Fixes reopening the reply editor when returning to a comment thread with an unsaved edit. - Fixes rich text annotation editor text selection spanning multiple nodes in the shadow DOM viewer variant. - Fixes measurement settings modal colors for built-in and custom dark themes. ### Loading, platform, and API reference - Fixes aborting `NutrientViewer.load()` with an `AbortSignal` hanging instead of rejecting when the SDK is rendered in an iframe. - Fixes a `ReferenceError` in the Node SDK when applying an `importDocument` document operation on Node.js 18 and 19, which have no global `File`. - Fixes corrupted type signatures and missing property descriptions on several API reference pages, along with the annotation class names shown for `defaultAnnotationsSidebarContent` and `defaultEditableAnnotationTypes`. For a full list of fixes, refer to the changelog. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. In server-backed mode, using `SearchType.WORD_BASED`, removing password protection during PDF export, and removing annotation notes after an XFDF roundtrip require Document Engine 1.16.0 or later. Document-defined annotation tab order requires Document Engine 1.18.0 or later. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.19 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.20.0 [web sdk 1.19 release notes]: /guides/web/release-notes/1-19/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [ui-customization]: /guides/web/user-interface/ui-customization/introduction/ [supported-slots]: /guides/web/user-interface/ui-customization/supported-slots/ [javascript]: /guides/web/forms/javascript-validation/ [gdpicture-changelog]: /guides/dotnet/changelog/#14.4.7 Lists important changes for Nutrient Web SDK 1.20]]> https://www.nutrient.io/guides/web/release-notes/1-19/ https://www.nutrient.io/guides/web/release-notes/1-19/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-18/ https://www.nutrient.io/guides/web/release-notes/1-18/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-17/ https://www.nutrient.io/guides/web/release-notes/1-17/ Wed, 07 Oct 2026 00:00:00 GMT { const root = document.createElement("div"); return { render: () => { // `getInstance()` is null until the instance is available; // `render` then runs again automatically once it is. root.textContent = getInstance() ? `Thread ${id}` : "Loading…"; return root; }, onMount: () => { // Rerun `render` whenever your own application state changes. myStore.subscribe(requestUpdate); }, }; }, }, }); ``` For more information, refer to the UI customization and supported slots guides. ### Improved text selection accuracy This release improves text selection accuracy. In Document Engine mode, this improvement requires Document Engine 1.17.0 or later once available. ### Accessibility Screen reader support is improved for annotations. When keyboard focus lands on a markup, ink, or shape annotation, the SDK now exposes the annotation’s referenced text, so assistive technologies announce the content the annotation refers to. ### Other additions - GdPicture is updated to 14.4.4. Refer to the GdPicture changelog for details. ### Performance, rendering, and stability - Fixes several Document Editor issues, including a crash when moving selected pages after a page in the same selection, inconsistent reordering when moving multiple selected pages, and a move dialog that could require two taps on mobile. - Fixes a range of Form Creator and form field issues: Editing a field’s name no longer makes it disappear until the next click, Control/Command-click no longer silently exits the active interaction mode, Shift-click now registers on the first widget when starting a multiselection, and newly created fields can be renamed repeatedly in standalone mode. - Fixes signature handling, including filling overlapping signature form fields, a selection flicker on filled signature fields, typed electronic signatures being cropped in RTL documents, and a raw localization key in the signature image picker. - Fixes measurement issues, including a loupe that could stay visible after pressing Escape, fractional precision labels showing an incorrect inch suffix for non-inch units, and an error and ghost label left behind after undoing an in-progress polygon area measurement. - Fixes several rendering issues, including thin white or colored lines in smooth background areas, squiggly text markup appearing truncated after resizing or zooming, search highlights making matched text unreadable in Safari, custom overlay items drifting from page content while scrolling, and rendering of zero-size and small pages in server-backed mode. - Fixes text annotation autofit so disabled autofit preserves manually resized bounding boxes when changing text properties and stops text selection toolbar items from appearing in the annotation toolbar. - Additional fixes across Instant JSON export (checkbox and radio button option labels) and standalone document loading for generic or missing MIME types. For a full list of fixes, refer to the changelog. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. However, `instance.exportPDF()` requires Document Engine 1.12.0 or later because earlier versions require legacy query-parameter authentication for the `/pdf` endpoint. In server-backed mode, using `SearchType.WORD_BASED`, removing password protection during PDF export, and removing annotation notes after an XFDF roundtrip require Document Engine 1.16.0 or later. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.16 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.17.0 [web sdk 1.16 release notes]: /guides/web/release-notes/1-16/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [ui-customization]: /guides/web/user-interface/ui-customization/introduction/ [supported-slots]: /guides/web/user-interface/ui-customization/supported-slots/ [gdpicture-changelog]: /guides/dotnet/changelog/#14.4.4 [document-engine-changelog]: /guides/document-engine/changelog/#1.17.0 Lists important changes for Nutrient Web SDK 1.17]]> https://www.nutrient.io/guides/web/release-notes/1-16/ https://www.nutrient.io/guides/web/release-notes/1-16/ Wed, 07 Oct 2026 00:00:00 GMT { // React to content editor session changes. }); ``` For more information, refer to the headless content editor and content editor API guides. ### Programmatic password handling for encrypted documents A new `onPasswordRequired` callback on `NutrientViewer.load()` lets you resolve passwords for encrypted documents in code instead of relying on the built-in prompt. It also supports documents that use the Dedicon encryption filter. ```js await NutrientViewer.load({ // ...your existing configuration onPasswordRequired: async () => { // Return the password from your own UI or secret store. return await getDocumentPassword(); }, }); ``` For more information, refer to the password-protected documents guide. ### Keyboard shortcut scoping The new `keyboardShortcutScope` option controls where the SDK’s keyboard shortcuts are captured. Two forms are supported. **`viewer` (default)** Shortcuts fire only while the user is interacting with the viewer, leaving the rest of the host page untouched: ```js await NutrientViewer.load({ // ...your existing configuration keyboardShortcutScope: { scope: "viewer" }, }); ``` **`global`** Restores document-wide capture for the actions you list in `interceptedActions`. Pass every action for the pre-1.16 behavior or a subset to capture some globally and keep the rest viewer-scoped: ```js await NutrientViewer.load({ // ...your existing configuration keyboardShortcutScope: { scope: "global", interceptedActions: [NutrientViewer.KeyboardShortcutActions.SEARCH], }, }); ``` The available actions are `SEARCH`, `PRINT`, `ZOOM`, `UNDO`, `REDO`, and `PAGINATION`. This release also fixes Command/Control-`+`/`-` zoom shortcuts in Firefox, which previously never fired because of a browser keycode difference. For more information, refer to the keyboard shortcuts guide. ### AI Assistant over HTTP MCP servers AI Assistant can now connect to HTTP MCP servers. A new public `AIAssistant.MCPHttpServerConfig` type and the `AIAssistant.AgentConfiguration.mcps` option let you wire the agent up to external tools and data sources you host. For more information, refer to the AI Assistant integration and AI agent tools guides. ### Opt-in debug logging A new opt-in debug logging mode surfaces detailed diagnostics to help track down initialization failures and other hard-to-reproduce issues. It’s off by default and safe to leave out of production builds. For more information, refer to the debug logging guide. ### Other additions - `ToolbarItemType` is now part of the public API, and the API documentation lists every valid toolbar item type value. - GdPicture is updated to 14.4.2. Refer to the GdPicture changelog for details. ### Performance, rendering, and stability - Fixes memory leaks that caused cumulative growth in DOM nodes, event listeners, and GPU memory across load and unload cycles in standalone mode, including cleanup of change-manager subscriptions, backend references, and electronic-signature font face style tags on unload. - Fixes an intermittent hang or blank render when loading multiple viewer instances concurrently in standalone mode. - Fixes an issue where the new page rendering architecture could display stale page content after zooming or scrolling. - Hardens XHTML sanitization for imported comments in standalone mode, closing a clickjacking gap that previously allowed inline styles and other disallowed markup. - Fixes password stripping when exporting PDFs in server-backed mode. - Fixes several core rendering and geometry issues, including DeviceCMYK transparency groups with multiply and overlay blend modes rendering too dark, clipped emojis in plain-text free text annotations, a crash on PDFs with malformed GoTo or GoToR link destinations, and page-margin and measurement-snapping errors on documents whose `CropBox` or `MediaBox` have a non-zero origin. - Additional fixes across the content editor, custom stamps, form fields, comments, measurement annotations, indexed full-text search, and dynamic font downloading. For a full list of fixes, refer to the changelog. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. However, `instance.exportPDF()` requires Document Engine 1.12.0 or later because earlier versions require legacy query-parameter authentication for the `/pdf` endpoint. In server-backed mode, using `SearchType.WORD_BASED`, removing password protection during PDF export, and removing annotation notes after an XFDF roundtrip require Document Engine 1.16.0 or later. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.15 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.16.0 [web sdk 1.15 release notes]: /guides/web/release-notes/1-15/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [keyboard-shortcuts-guide]: /guides/web/knowledge-base/add-custom-keyboard-shortcuts/ [keyboard-shortcut-scoping]: #keyboard-shortcut-scoping [password-protected-guide]: /guides/web/features/password-protected-pdfs/ [headless-content-editor]: /guides/web/headless/content-editor/ [content-editor-api]: /guides/web/editor/content-editor-api/ [ai-assistant-guide]: /guides/web/ai-assistant/integrate-with-ai-assistant/ [ai-agent-tools-guide]: /guides/web/ai-assistant/ai-agent-tools/ [debug-logging-guide]: /guides/web/troubleshooting/debug-logging/ [gdpicture-changelog]: /guides/dotnet/changelog/#14.4.2 Lists important changes for Nutrient Web SDK 1.16]]> https://www.nutrient.io/guides/web/release-notes/1-15/ https://www.nutrient.io/guides/web/release-notes/1-15/ Wed, 07 Oct 2026 00:00:00 GMT ({ render: () => createToolbar(instance), }), }, }, }); ``` After: ```js NutrientViewer.load({ ui: { tools: { main: (getInstance, id) => ({ render: () => createToolbar(getInstance()), }), }, }, }); ``` The change applies to every `ui.*` slot, including: - Preload slots — `ui.loader`, `ui.passwordPrompt`. - Postload slots — `ui.tools.main`, `ui.tools.contextual`, `ui.annotations.*`, `ui.signatures.*`, `ui.search`, `ui.documentEditor`, `ui.commentThread`, `ui.sidebar.*`. ### Headless annotation APIs This release introduces an `annotations.*` namespace on `instance` for working with annotations programmatically, organized by annotation type. Each sub-namespace exposes type-specific operations and shares a common selection, note, and clipboard infrastructure — usable without mounting the full viewer UI: - `annotations.ink` - `annotations.link` - `annotations.measurement` - `annotations.redaction` - `annotations.shape` - `annotations.textMarkup` - `annotations.text` The shared infrastructure is extensible — additional annotation types can plug into the same primitives. This is the foundation for richer headless and automation workflows. For more information, refer to the headless annotations overview, headless measurement annotations, and headless redaction annotations. Let us know through our support form which patterns you’d like to see expanded next. ### Cancelable load and conversion operations `NutrientViewer.load()`, `convertToPDF()`, `convertToOffice()`, and `populateDocumentTemplate()` now accept an `AbortSignal` to cancel in-flight operations. This is useful when users navigate away mid-load or you need to terminate a slow conversion: ```js const controller = new AbortController(); const instance = await NutrientViewer.load({ // ...your existing configuration signal: controller.signal, }); // Later, to cancel: controller.abort(); ``` For more information, refer to the viewer troubleshooting, Office-to-PDF conversion, PDF-to-Office conversion, and Word template generation guides. ### Configurable loader UI A new `ui.loader` option controls what users see while a document loads. Three forms are supported: **`skeleton` (default)** — A realistic placeholder of the viewer layout that reduces perceived load time: ```js await NutrientViewer.load({ // ...your existing configuration ui: { loader: { type: "skeleton" } }, }); ``` **`progress`** — The indeterminate spinner with a determinate progress bar (the pre-1.15 default): ```js await NutrientViewer.load({ // ...your existing configuration ui: { loader: { type: "progress" } }, }); ``` **Slot callback** — Fully replace the loader with custom DOM. Because the loader renders before `NutrientViewer.load()` resolves, `getInstance()` may return `null` inside this slot; use it for loading UI only: ```js await NutrientViewer.load({ // ...your existing configuration ui: { loader: (getInstance, id) => ({ render: () => { const div = document.createElement("div"); div.innerText = "Loading your document..."; return div; }, }), }, }); ``` To hide the loader entirely, return `null` from `render`: `(getInstance, id) => ({ render: () => null })`. ### Whitespace-tolerant search A new opt-in, `SearchType.WORD_BASED`, makes `instance.search()` resilient to whitespace inconsistencies in extracted PDF text. The mode strips Unicode space variants (NBSP, em/en/thin spaces, ideographic space, etc.) plus tab/newline/CR from both the query and the document before matching, so multiline phrases that cross tables, columns, or line wraps with stray whitespace match cleanly. Annotation contents are matched with the same algorithm. Punctuation is preserved on both sides, and case-insensitive search (the default) now case-folds non-ASCII letters too — `"MÖCHTEN"` matches `"möchten"`. ```js const results = await instance.search("Smith, John", { searchType: NutrientViewer.SearchType.WORD_BASED, }); ``` Default `instance.search()` behavior is unchanged. Additionally, the existing smart-search regex now tolerates a single space immediately before a line break, fixing cases where PDF text extraction inserts a trailing space at line wraps and a clean-newline query failed to match. {% alert line="single-line" icon="dotted/info" %} `SearchType.WORD_BASED` is available in Web SDK standalone mode immediately. Server-backed mode requires Document Engine 1.16.0 or later. {% /alert %} For more information, refer to the text search and built-in search UI guides. ### Performance, fonts, and stability - Dynamic font downloading and font substitution now work for linearized PDF loads, eliminating font-related fallbacks during progressive loading. - A new API lets you control the visual rendering order of annotations on a page via a custom comparator function. - Document Crop mode now supports keyboard input — arrow keys draw the crop region, Enter confirms, and Escape cancels. - The standalone JWT signing service now forwards the `flatten` flag consistently from `prepareSign` to the `/sign_hash` request, producing valid signatures when `instance.signDocument()` is called with `flatten: true`. - Fixes a regression introduced in 1.14.0 where cross-user updates to non-comment annotations could be rejected by Document Engine with `invalid_anonymity_update`, blocking collaborative editing of existing annotations. - Additional fixes across RTL viewer trackpad scrolling and scrollbar visibility, IME composition in custom stamp text fields, content editor text drag-selection on Windows, ligature text selection, redaction font sizing, Arabic rich-text free text appearance streams, and several content editor and form creator edge cases. For more information, refer to the font substitution, linearized downloads, crop, and annotation customization guides. {% alert line="multi-line" %} Document Engine 1.5.6 or later can run this release. However, `instance.exportPDF()` requires Document Engine 1.12.0 or later because earlier versions require legacy query-parameter authentication for the `/pdf` endpoint. In server-backed mode, `SearchType.WORD_BASED` requires Document Engine 1.16.0 or later. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For more information, refer to the UI customization introduction, supported slots reference, and slot examples guides. For a complete list of changes, bug fixes, and improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.14 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.15.0 [web sdk 1.14 release notes]: /guides/web/release-notes/1-14/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [searchtype-api]: /api/web/enums/NutrientViewer.SearchType.html [abortsignal]: https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal [ui-loader-api]: /api/web/interfaces/UI.Configuration.html#loader [support-form]: https://support.nutrient.io/hc/en-us/requests/new [viewer-troubleshooting]: /guides/web/viewer/troubleshooting/ [office-to-pdf]: /guides/web/conversion/office-to-pdf/ [pdf-to-office]: /guides/web/conversion/pdf-to-office/ [from-word-template]: /guides/web/pdf-generation/from-word-template/ [headless-overview]: /guides/web/headless/ [headless-measurement]: /guides/web/headless/measurement/ [headless-redaction]: /guides/web/headless/redactions-from-selection/ [ui-customization-introduction]: /guides/web/user-interface/ui-customization/introduction/ [supported-slots]: /guides/web/user-interface/ui-customization/supported-slots/ [ui-slot-examples]: /guides/web/user-interface/ui-customization/examples/ [text-search-guide]: /guides/web/features/customized-search/ [built-in-search-ui]: /guides/web/search/built-in-ui/ [font-substitution-guide]: /guides/web/viewer/fonts/substitution/ [linearized-downloads-guide]: /guides/web/viewer/linearized-downloads/ [crop-guide]: /guides/web/editor/page-manipulation/crop/ [annotation-customization-guide]: /guides/web/annotations/custom-rendered-annotations/ Lists important changes for Nutrient Web SDK 1.15]]> https://www.nutrient.io/guides/web/release-notes/1-14/ https://www.nutrient.io/guides/web/release-notes/1-14/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-13-1/ https://www.nutrient.io/guides/web/release-notes/1-13-1/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-13/ https://www.nutrient.io/guides/web/release-notes/1-13/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-12/ https://www.nutrient.io/guides/web/release-notes/1-12/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-11/ https://www.nutrient.io/guides/web/release-notes/1-11/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-10/ https://www.nutrient.io/guides/web/release-notes/1-10/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-9/ https://www.nutrient.io/guides/web/release-notes/1-9/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-8/ https://www.nutrient.io/guides/web/release-notes/1-8/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-7/ https://www.nutrient.io/guides/web/release-notes/1-7/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-6/ https://www.nutrient.io/guides/web/release-notes/1-6/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-5/ https://www.nutrient.io/guides/web/release-notes/1-5/ Wed, 07 Oct 2026 00:00:00 GMT Tab key, ensuring consistent accessibility across interaction methods. ### Enhanced annotation capabilities Version 1.5 brings significant refinements to the annotation experience, with a focus on color handling, mobile usability, and user interface consistency. #### Improved color handling The text color palette in annotations has been improved with a streamlined color selection interface. The transparent swatch option has been removed, creating a more intuitive color selection experience with only functional color options available. This refinement ensures that all available color choices behave consistently and predictably. Additionally, we’ve enhanced the 'None' color selection functionality for font and background colors when working with multiple text selections. The 'None' option can now be selected even if it’s currently active, and color selections are consistently applied across all selected text, ensuring uniform behavior across all annotation types. #### Enhanced mobile experience We’ve fixed an issue where the comment drawer didn’t open properly on mobile devices. This fix ensures comments are now accessible across all device types and screen sizes, allowing users to seamlessly interact with comment marker annotations in mobile view. #### User interface refinements We’ve fixed an issue where layout configuration icons didn’t update when custom icons were passed via API. This fix allows developers to maintain a consistent visual language throughout their applications by ensuring custom icons are properly displayed. We’ve also fixed an issue where users were able to submit blank typed signatures: The “Done” button is now disabled until at least one visible character is entered, ensuring signatures contain meaningful content and preventing potential errors. Additionally, we’ve addressed a problem where the Document Editor image gallery didn’t auto-scroll during drag operations. This fix restores the ability to drag pages beyond the visible viewport during page reordering. For example, when reordering pages in a multipage document, the editor now automatically scrolls when a dragged page reaches the edge of the visible area. ### Core functionality and document handling This release delivers substantial improvements to the core functionality of the SDK, with a focus on comments, document comparison, security, and rendering accuracy. #### Comments UI Previously, comments threads were always displayed in a floating sidebar to the side of the page, which wasn’t convenient as soon as the page was zoomed in and there wasn’t enough space left to show the comments without having to scroll the viewport. In this release, the comments sidebar is now only shown when there’s enough space to display it without scrolling. If there isn’t enough space, the comments are shown in a popover instead, which can be opened by clicking on the comment marker. This popover dialog was previously visible only in `FIT_TO_WIDTH` zoom mode. We understand that this change may not be ideal for all use cases, so we now provide an extension to the `NutrientViewer.ViewState` API that makes it possible to customize this behavior at any time by setting `NutrientViewer.ViewState#commentDisplay`: - `NutrientViewer.CommentDisplay.FITTING` — The default value; will show comments in a floating sidebar by the page side when there’s enough space to do so, and in a popover when there isn’t, and the marker annotation is selected. - `NutrientViewer.CommentDisplay.FLOATING` — Will always show comments in a floating sidebar by the page side. - `NutrientViewer.CommentDisplay.POPOVER` — Will always show comments in a popover when the marker annotation is selected. As an example of how it’s used, here’s how to set the `commentDisplay` so the comments UI behaves like in previous versions, always showing comments in a floating sidebar unless in `FIT_TO_WIDTH` zoom mode: ```js const instance = await NutrientViewer.load(config); instance.setViewState((viewState) => viewState.set("commentDisplay", NutrientViewer.CommentDisplay.FLOATING), ); instance.addEventListener( "viewState.change", function (viewState, previousViewState) { const zoom = typeof viewState.zoom === "object" ? viewState.zoom.zoomMode : viewState.zoom; const previousZoom = typeof previousViewState.zoom === "object" ? previousViewState.zoom.zoomMode : previousViewState.zoom; if ( previousZoom === zoom && viewState.commentDisplay === previousViewState.commentDisplay ) { return; } if ( zoom === NutrientViewer.ZoomMode.FIT_TO_WIDTH && viewState.commentDisplay !== NutrientViewer.CommentDisplay.POPOVER ) { instance.setViewState((viewState) => viewState.set("commentDisplay", NutrientViewer.CommentDisplay.POPOVER), ); } else if ( viewState.commentDisplay !== NutrientViewer.CommentDisplay.FLOATING ) { instance.setViewState((viewState) => viewState.set("commentDisplay", NutrientViewer.CommentDisplay.FLOATING), ); } }, ); ``` #### Enhanced document comparison and XFDF support Word-level text comparison has been added, providing more granular document comparison capabilities that allow users to identify changes with greater precision. Previously, all comparisons were done at the character level, which could result in unintuitive highlighting of changes. For example, changing “January” to “February” would show as a deletion of “Jan,” addition of “Febr,” and “uary” as unchanged. With word-level comparison, the entire word is highlighted as changed, creating a more intuitive and readable comparison. Configuration options for rich text when working with XFDF files have also been added, expanding the SDK’s flexibility when working with this format and ensuring consistent rich text handling across different document workflows. This enhancement allows for better propagation of rich text configuration from the Web SDK to Core and Document Engine backends when performing XFDF operations. #### Security and performance improvements The Content Security Policy (CSP) HTTP header required `unsafe-eval` to be set in recent versions. You may now use `wasm-unsafe-eval` instead. We’ve also updated GdPicture to version 14.3.9, bringing the latest improvements from this underlying technology to our SDK. #### Rendering and UI consistency Several rendering issues have been addressed to ensure accurate display of annotations and content: - Fixed an issue where text markup annotations were rendered with the wrong proportions when zoomed, and in the wrong direction on rotated pages. This fix ensures markup annotations like squiggly, strikethrough, and underline now maintain appropriate proportions regardless of zoom level, page rotation, or text size, improving overall readability. - Fixed an issue where moving a stamp annotation rotated at 45 degrees would resize it. This fix ensures stable dimensions for rotated stamps throughout all user interactions, preventing unwanted size changes during movement. - Fixed an issue where comment threads would appear clipped in narrow screen widths. This fix ensures comment boxes now remain fully visible and accessible, even when the viewport is narrow or when using high zoom levels. - Fixed an issue where the comments sidebar and popover were simultaneously visible in `FIT_TO_WIDTH` view mode. This fix creates a more consistent and less cluttered user interface. #### Form handling and stability - Fixed an issue where it wasn’t possible to correctly set the time in some time form fields. This fix ensures users can now properly set time values across all platforms, with consistent validation behavior and support for proper time formats on both desktop and mobile devices. - Fixed an issue where using some Form Creator and Measurements dropdowns would throw an error. This fix resolves problems with Shadow DOM compatibility, ensuring consistent behavior when creating and managing form fields and annotations. - Fixed an issue where the first new comment text field wouldn’t be focused when creating a comment, improving workflow efficiency. Additionally, we’ve fixed a crash that could occur when creating a text parser for a page with verbose logging enabled, ensuring consistent performance, even with complex document structures. {% alert line="multi-line" %} Document Engine 1.5.6 or later is compatible with this release. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and performance improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.4 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /changelog/web/#1.5.0 [web sdk 1.4 release notes]: /guides/web/release-notes/1-4/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [bui-migration]: /guides/web/migration-guides/baseline-ui-migration-guide/ Release notes for Nutrient Web SDK 1.5 highlighting new capabilities, API refinements, viewer/UI updates, and upgrade guidance.]]> https://www.nutrient.io/guides/web/release-notes/1-4/ https://www.nutrient.io/guides/web/release-notes/1-4/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-3/ https://www.nutrient.io/guides/web/release-notes/1-3/ Wed, 07 Oct 2026 00:00:00 GMT ) now render as expected, and annotation tool states (e.g. selected or disabled) reflect correctly in the UI. ### Improved accessibility and metadata handling Nutrient Web SDK 1.3 brings better support for preserving accessibility-related metadata. `PDF/UA` tags are now retained when documents are edited, ensuring compliance with accessibility standards. The primary document language is also preserved, allowing assistive technologies to accurately interpret and present content. Alert and confirm dialogs are now properly centered, and focus is automatically directed to dialog buttons, improving keyboard accessibility. ### Expanded rendering and scripting capabilities This release adds support for several advanced features in the PDF JavaScript API, including `AFTime_KeystrokeEx`, the JavaScript `global` object, and page-level open and close actions. These additions enable more dynamic, form-driven documents with behavior that closely matches native PDF viewers. When converting Excel documents, developers can now specify maximum spreadsheet dimensions, and tile size is configurable for rendering optimization. We’ve also introduced a more resilient rendering path for callout and free text annotations to ensure appearance streams fit within annotation bounds. Loading speeds for Office documents have been improved, and launching Content Editor on pages with dense vector graphics (such as architectural plans) is now more responsive. ### Behavioral changes The `GoToAction` behavior has changed: It now sets destinations based on page references instead of page indexes. This means links will remain accurate, even if pages are moved or removed in the document editor. {% alert line="multi-line" %} Document Engine 1.5.6 or later is compatible with this release. See the Web SDK and Document Engine compatibility requirements. {% /alert %} ### Breaking changes **PDF ID encoding correction** This release includes a fix to how PDF trailer IDs are encoded in the `pdfId` field of Instant JSON. Previously, the encoding was incorrectly truncated, resulting in shorter `pdfId` values. The corrected behavior now properly encodes the complete PDF ID. **Impact:** If you have existing Instant JSON files created with SDK versions prior to 1.3.0, they’ll contain `pdfId` values that won’t match when loading the same PDF in version 1.3.0 or later. This will result in a “Permanent PDF ID mismatch“ error. **Migration options** 1. **Remove pdfId validation** (recommended for most cases) — Strip the `pdfId` property from existing Instant JSON: ```javascript const { pdfId, ...jsonWithoutPdfId } = existingInstantJSON; NutrientViewer.load({ instantJSON: jsonWithoutPdfId, }); ``` 2. **Update existing Instant JSON** — Reexport your Instant JSON files using version 1.3.0 or later to generate corrected `pdfId` values. {% alert line="single-line" %} Removing `pdfId` is safe if your application ensures the correct PDF is loaded with its corresponding Instant JSON. {% /alert %} For a complete list of changes, bug fixes, and performance improvements, refer to the changelog. For previous release notes, refer to the Web SDK 1.2 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /guides/web/changelog/#1.3.0 [web sdk 1.2 release notes]: /guides/web/release-notes/1-2/ [ai text comparison guide]: /guides/web/comparison/compare-text-ai/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility Explore Nutrient Web SDK 1.3 changes, including new APIs, stability fixes, rendering improvements, and steps for upgrading existing apps.]]> https://www.nutrient.io/guides/web/release-notes/1-2/ https://www.nutrient.io/guides/web/release-notes/1-2/ Wed, 07 Oct 2026 00:00:00 GMT viewState.set("enableAlwaysScrollToZoom", true) ); ``` After: ```js // Always zoom on scroll wheel without requiring the Control key to be pressed. instance.setViewState( new NutrientViewer.ViewState({ zoom: { // Configure scroll wheel zoom behavior. wheelZoomMode: NutrientViewer.WheelZoomMode.ALWAYS // ... other zoom options } }) ); ``` ### Rich text annotations: Major enhancements This release delivers significant improvements to rich text annotations, making them more reliable, consistent, and user-friendly. Key enhancements - Adds support for applying font size and font family to individual text segments, enabling more precise text styling. - Standardizes behavior between background color and font color selections, ensuring consistent functionality across all color options. - Synchronizes rich text properties with underlying annotation metadata when all text is selected, ensuring consistent display. - Improves text formatting (bold, italic, underline) to work reliably during typing without disrupting line breaks or causing text to become hidden. - Enhances color management to maintain focus when changing colors, with proper updating of color swatches and consistent color application. - Preserves formatting and prevents data loss in multi-line text annotations during editing, deletion, and focus changes. - Maintains styling and formatting when pasting rich text content, with proper placement of pasted text. - Ensures consistent resizing behavior across all handles while preserving an annotation’s size, formatting, and alignment. - Improves keyboard focus management and restoration in the toolbar for consistent behavior across browsers. - Enhances AP stream generation with proper preservation of newlines and text formatting for improved document compatibility. Nutrient Web SDK 1.2 release notes detailing new features, annotation and UI updates, performance tuning, and migration considerations.]]> https://www.nutrient.io/guides/web/release-notes/1-1/ https://www.nutrient.io/guides/web/release-notes/1-1/ Wed, 07 Oct 2026 00:00:00 GMT https://www.nutrient.io/guides/web/release-notes/1-0/ https://www.nutrient.io/guides/web/release-notes/1-0/ Wed, 07 Oct 2026 00:00:00 GMT viewState.set("enableAlwaysScrollToZoom", true), ); ``` After: ```js instance.setViewState((viewState) => viewState.set("zoom", { // Configure scroll wheel zoom behavior. wheelZoomMode: NutrientViewer.WheelZoomMode.ALWAYS, // ... other zoom options. }), ); ``` ### UI updates This release introduces a major update to the Web SDK’s user interface, with the following UI sections migrated: - Link annotation toolbar - Image and signature annotation (image) toolbar - Stamp annotation toolbar - Text highlight and markup annotation toolbar - Content editor toolbar - Form creator toolbar - Ink eraser toolbar - Note annotation toolbar - Redaction toolbar - Shape annotation toolbars - Document crop toolbar Most customizations will continue to work as before, but if you notice anything unexpected and you were using CSS classes or CSS variables for customization, our Baseline UI migration guide offers helpful tips and guidance. ### Toolbars UI migration Annotation toolbars have undergone a significant overhaul to improve accessibility and customization capabilities, leveraging our in-house Baseline UI design system. These changes bring them in line with the updated look of other UI components, such as the sidebar and main toolbar, while also enhancing support for users’ accessibility requirements. ### Text Comparison API changes Several updates have been made to the Text Comparison API to ensure consistency with documentation and to unify data handling. 1. `TextBlock.rects` renamed to `TextBlock.rect` **Previous behavior:** `TextBlock.rects` was documented, but no rects were returned. **Impact:** Use `TextBlock.rect` instead of `TextBlock.rects`. 2. `TextBlock.rect` coordinates format updated **Previous behavior:** Coordinates were returned using a PDF coordinate system. **Impact:** If your application relied on PDF-style coordinates, update your logic to accommodate the new `x`, `y`, `width`, `height` format. 3. `Operation.originalTextBlocks` and `Operation.changedTextBlocks` return arrays **Previous behavior:** Only one `TextBlock` object was documented to be returned. **Impact:** These now return an array of `TextBlock` objects. Make sure your code handles multiple items. 4. `PageComparisonResult.originalPageIndex` and `PageComparisonResult.changedPageIndex` are optional **Previous behavior:** These properties were always present. **Impact:** Your code should now handle the possibility that these values may be undefined — particularly when comparing documents with differing page counts. ### Signing document hashes via DWS Processor API and Document Engine This release adds a new signing API, which enables direct hash signing with Document Engine and DWS Processor API when Web SDK operates client-side in the browser. An access token just needs to be passed to the `signDocument` method. Learn more in our guides on how to sign via DWS Processor API and how to sign via Document Engine. ### Attachments sidebar and preview A new attachments sidebar has been added. It displays a list of all files embedded in a PDF, and users can preview these files directly in the viewer or download them if the file format is unsupported. Previewing files is unavailable when using Document Engine — in this case, files can only be downloaded. {% alert line="multi-line" %} Document Engine 1.5.6 or later is compatible with this release. See the Web SDK and Document Engine compatibility requirements. {% /alert %} For a complete list of changes, bug fixes, and performance improvements, refer to the changelog. For the previous release notes, see Web SDK 2024.7 release notes. We appreciate your feedback and contributions as we continue to enhance Nutrient Web SDK. [changelog]: /changelog/web/#1.0.0 [`nutrientviewer.viewstate#enablealwaysscrolltozoom`]: /api/web/classes/NutrientViewer.Instance.html#enablealwaysscrolltozoom [`viewstate.zoom api`]: /api/web/classes/NutrientViewer.ViewState.html#zoom [web sdk 2024.7 release notes]: /guides/web/release-notes/2024-7/ [dws sign]: /guides/web/signatures/digital-signatures/signature-lifecycle/sign-a-pdf-document-dws/ [de sign]: /guides/web/signatures/digital-signatures/signature-lifecycle/sign-a-pdf-document-document-engine/ [web sdk and document engine compatibility requirements]: /guides/document-engine/viewer/client-integration/web/#version-compatibility [bui-migration]: /guides/web/migration-guides/baseline-ui-migration-guide/ Release notes for Nutrient Web SDK 1.0 covering the rebrand, new npm package, API changes, performance fixes, and upgrade guidance.]]> https://www.nutrient.io/guides/web/release-notes/upgrading/ https://www.nutrient.io/guides/web/release-notes/upgrading/ Wed, 07 Oct 2026 00:00:00 GMT