This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/ios/releases/26-12.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Nutrient iOS SDK 26.12 release notes

Nutrient iOS SDK 26.12 release notes

RSS

24 August 2026

Nutrient iOS SDK 26.12 makes the Content Editor faster and adds full support for entering Korean text. It also renders print-oriented documents with much better color fidelity, matching Adobe Acrobat, with new render options to control this behavior.

This release contains several fixes and enhancements. For the full list of changes, see our changelog.

Looking ahead to iOS 27 and Xcode 27

Nutrient iOS SDK 26.12 should be used with Xcode 26.5. While we haven’t observed compatibility issues running on the iOS 27 beta with this combination, we’re also working on full Xcode 27 and iOS 27 compatibility for our upcoming release. We expect it shortly after Apple’s Xcode 27 RC ships in September. We’ll switch our nightly builds to Xcode 27 in the coming weeks.

Faster, more reliable Content Editor

The Content Editor lets your users edit the original text of a PDF directly on the page. With Nutrient iOS SDK 26.12, it fully supports entering Korean text: We fixed incremental Hangul syllable composition for Korean 2-set input, so jamo entered using the Korean keyboard are now correctly combined into Hangul syllable blocks as you type, just like in standard system text fields.

In addition, the Content Editor now starts faster by reusing cached fonts across editing sessions.

Accurate colors for print-oriented documents

Documents prepared for professional printing often use overprint settings, spot colors, and CMYK transparency. Previously, some of these documents rendered with washed-out colors, missing thin lines, or page content that didn’t match Adobe Acrobat. This release fixes a range of these rendering issues, and overprinting is now simulated automatically for content that requests it — matching Acrobat’s “Overprint Preview: Auto” behavior.

Two new properties control rendering fidelity. Set RenderOptions.overprintPreview to .disabled if you prefer the previous rendering without overprint simulation. Set RenderOptions.blackRendering to .pureBlack to render 100K CMYK black as true black instead of the color-managed dark tone that matches Acrobat. Apply these before a document is first rendered:

document.updateRenderOptions(for: .all) { options in
    options.overprintPreview = .disabled
    options.blackRendering = .pureBlack
}

More changes

Form field calculations that depend on other calculated fields now resolve fully, even when the document lists them out of order in its calculation order, matching Acrobat. Form scripts using default parameter values in PDF JavaScript are now supported, and text form fields with a fixed font size in a tightly sized box no longer reject typed input.

We also fixed continuous document reloading, visible as flickering, with cloud storage providers such as OneDrive that update file metadata after a file is read.