Overview
The Wacom Ink SDK for ink — previously published under the WILL™ (Wacom Ink Layer Language) name — is the toolkit for applications where handwriting itself is the data. It captures pen strokes as digital ink rather than as an image, preserving the geometry and dynamics of every stroke so that the writing can be re-rendered cleanly at any size, edited, searched, replayed in the order it was written, or exported to another system without loss.
That distinction matters most in note-taking, education, form annotation, design review and inspection applications. A student’s worked solution, an engineer’s mark-up on a drawing, a surveyor’s annotation on a site plan: each is handwriting that has to remain meaningful later, not a flat picture pasted into a file. Because the ink is stored as structured data, an application can do things a scanned image makes impossible — replaying how an answer was reached, or scaling a mark-up without it degrading.
Underneath it sits Wacom’s Universal Ink Model, a language-neutral and platform-neutral data model for representing digital ink. Its purpose is portability: ink captured in one application on one platform stays usable in another, rather than being locked into a proprietary format. For organisations building across web, desktop and mobile, that is usually the deciding factor, because it avoids re-implementing ink handling separately for each environment.
Be clear about what this is not. It is a general-purpose digital ink toolkit, not a signing solution — it does not capture signatures for legal approval, produce signed PDFs, or verify anyone’s identity. If your requirement is a signature on a document, use the Wacom Ink SDK for signature or sign pro PDF API instead. This SDK also carries the highest development effort of the Wacom range, because it gives you building blocks rather than a finished workflow.
Wacom Ink SDK for Ink at a Glance
| Purpose | Capturing, storing, rendering and replaying digital ink in your own application |
|---|---|
| Former name | WILL™ SDK for ink (Wacom Ink Layer Language) |
| Underlying data model | Universal Ink Model – language-neutral and platform-neutral |
| Ink captured as | Structured stroke data rather than a flat image |
| Typical capabilities | Re-rendering at any scale, editing, replay of stroke order, export between systems |
| Devices | Wacom pen tablets, pen displays and other pen-enabled hardware |
| Typical applications | Note-taking, education, form annotation, design review, field inspection |
| Related Wacom toolkit | Pen and touch data access for reading raw pen and touch input |
| Not intended for | Document signing or signature verification – use the signature SDK or sign pro PDF API |
| Best suited to | Product and development teams building ink-centric applications |
Which Wacom SDK Do I Need?
Five Wacom products cover signing, and they are not interchangeable. This table is the short version of the advice we give clients before any integration work is scoped.
| Product | Use it when you need to… | Platforms | Development effort |
|---|---|---|---|
| Wacom Ink SDK for signature | Capture a handwritten signature with biometric data inside your own application | Windows, iOS, Android | Moderate – you build the surrounding workflow |
| sign pro PDF API | Sign complete PDF documents from an existing CRM, ERP or contract system | Windows, iOS, Android | Light to moderate – document handling is provided |
| sign pro PDF app | Sign and fill PDFs by hand with no integration at all | Windows | None – install and use |
| Wacom Ink SDK for verification | Check whether a signature matches reference samples already on file | See product page | Moderate – scoring integrated into your process |
| Wacom Ink SDK for ink | Capture, store and replay digital ink generally – notes, annotation, forms | Multiple | Moderate to high – a toolkit, not a solution |
Not sure which fits your process? Talk to our integration team — we scope this against your actual systems before recommending anything.
Frequently Asked Questions
What is the Wacom Ink SDK for ink?
It is a development toolkit for applications that capture handwriting as digital ink. Strokes are stored as structured data rather than as an image, so the writing can be re-rendered, edited, replayed or exported without losing quality or detail.
Is this the same as the WILL SDK?
Yes. It was previously published as the WILL™ SDK for ink, named after the Wacom Ink Layer Language. Wacom has since consolidated its developer range under the Wacom Ink SDK name; the purpose of the toolkit is unchanged.
What is the Universal Ink Model?
It is Wacom’s language-neutral and platform-neutral data model for representing digital ink. It exists so ink captured in one application or platform remains usable in another, instead of being locked into a proprietary format.
Can I use it to capture signatures?
Not for signing purposes. This toolkit handles digital ink generally and does not produce signed documents or verify identity. For signatures on documents, use the Wacom Ink SDK for signature or sign pro PDF API.
How is digital ink better than saving an image?
An image is a flat picture; digital ink keeps the strokes as data. That allows an application to scale writing without degrading it, edit or erase individual strokes, replay the order it was written in, and pass it to other systems intact.
How much development work does it involve?
More than the other Wacom kits. It provides building blocks rather than a finished workflow, so your team designs the application around it. We can scope that work if you are considering an ink-based product.
Building an application around digital ink? Talk to us about devices, licensing and development support for Wacom Ink SDK projects in the UAE.