What Is in the SDK
Two Swift frameworks. DocumentCore reads and writes the files; AppleRender draws their pages.
DocumentCore: Read, Edit, and Save
Parses .docx, .xlsx, and .pptx into structured, immutable scenes: paragraphs, runs, tables, and sections; sheets, cells, and formulas; slides and shapes. Derive an edited scene and save it: only the parts you changed are regenerated, and everything else in the file is carried over untouched.
AppleRender: Pages, Images, and PDF
Lays documents out with Core Text and Core Graphics and renders any page to an image or to PDF. Word documents flow into pages, spreadsheets paginate for print sheet by sheet, and each slide is a page.
A Formula Engine
Evaluates spreadsheet formulas. Excel-style error values such as #DIV/0! and #REF! come back as cell values, never as exceptions.
Fonts Included
Metric-compatible fonts for Calibri and Cambria ship with the SDK, so documents set in them lay out at the right size. Other fonts come from the system, with a fallback cascade that handles Chinese, Japanese, and Korean text.
Built to Ship in Your App
What you would otherwise have to check for yourself before putting a document engine in front of customers.
- No network, ever. Your licence is a signed line verified on the device, so a document never leaves your app, and a sandboxed app needs no network entitlement for licensing.
- Typed errors. A file the engine cannot read produces an error that names the part and the reason; document input never crashes your app.
- Safe to run in parallel. Scenes are Sendable value types, and the parsers, writers, and renderer are stateless, so different documents can be processed at the same time.
- Two ways to add it. Add the package from GitHub, and Swift Package Manager downloads the two frameworks from its release and verifies their checksums; or take the zip each release attaches, a folder with the frameworks, the documentation, and the samples, and add it as a local package.
Platforms
iOS 16 and iPadOS 16 or later, and macOS 13 or later.
Formats
.docx, .xlsx, .xlsm, and .pptx in; the same formats, page images, and PDF out. An .xlsm workbook's macros are kept byte for byte and never run.
Documentation
An API reference for both frameworks, with guides to getting started, licensing, errors and threading, rendering, and working with Word, spreadsheet, and presentation files. Read it online.
What It Does Not Do
So you can tell early whether it fits.
No PDF Editing
ComOfficeKit renders documents to PDF. It does not open, annotate, or edit PDF files.
No User Interface
It has no editor or viewer screens. You build the interface; the SDK supplies the document model and draws the pages.
Apple Platforms Only
This SDK runs on iOS, iPadOS, and macOS. Windows has an SDK of its own, ComOfficeKit for Windows; tell us which other platform you need.
Frequently Asked Questions
How do I get ComOfficeKit?
Add it from GitHub with Swift Package Manager. Its README publishes a free evaluation key, valid for about 60 days, so you can try the whole SDK without signing up. For a licence, tell our sales team about your project on the contact form, or write to support@comofficekit.com.
Does it need a network connection?
No. The licence is verified on the device and the SDK makes no network call at any point, so documents stay inside your app.
Which versions of iOS and macOS does it support?
iOS and iPadOS 16 or later, and macOS 13 or later.
Can it open PDF files?
No. ComOfficeKit works with .docx, .xlsx, .xlsm, and .pptx files and renders them to PDF. It does not open or edit PDF documents.
Is it the same engine as LynxOffice?
Yes. LynxOffice is built on the same document engine, so the SDK reads and renders files the way the app does.
Talk to Us About ComOfficeKit
Tell us what you are building and which platforms you need, and our sales team will get back to you. You can also write to support@comofficekit.com.