Open `.zpl` label source directly in SharePoint with a dedicated viewer shell, a read-only source pane, and a preview-focused workflow that stays inside your browser.
Teams that work with Zebra label templates often store them in SharePoint, but SharePoint treats `.zpl` files as plain downloads. That breaks review workflows and makes even simple checks slower than they should be.
ZPL Files for SharePoint gives your team a purpose-built place to open and inspect those files without leaving the document library. The current release focuses on the viewer shell first: source inspection, sizing controls, licensing chrome, and the workflow foundation for richer rendering in the next step.
Open supported files in a modal experience built for label source, not generic text previews.
Inspect the raw ZPL alongside the preview area without downloading the file to your desktop first.
Set width, height, units, density, and label index so the preview workflow is ready for rendering integration.
The add-in downloads the file from SharePoint and handles it locally in the browser. No third-party viewer service is required.
The current viewer targets Zebra Programming Language source files stored with the `.zpl` extension.
Pick one file in your SharePoint document library. The `View ZPL` command appears when the selection is supported.
The add-in downloads the file from SharePoint and opens a modal viewer without sending the file to an external service.
Use the read-only source pane and the preview controls to review the file before richer rendering and editing capabilities land in later releases.
Install the add-in, select a `.zpl` file in your document library, and click `View ZPL` in the command bar.
No. The add-in downloads the file from SharePoint and handles it locally in the browser.
Not in this release. The first milestone focuses on nailing the viewer shell and source workflow. Editing comes next.
The current build provides the layout, source parsing, label counting, and preview controls so the rendering library can slot in cleanly in the follow-up release.
Start with the viewer shell now, then grow into richer rendering and editing workflows over time.