Design
Zeplin
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Zeplin, Inc. · zeplin.io
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Zeplin at a glance
- Vendor
- Zeplin, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Zeplin 2.5/5, the mean of 6 judges. Zeplin is a handoff product you publish designs into from Figma, Sketch, Adobe XD or Photoshop. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zeplin is a handoff product you publish designs into from Figma, Sketch, Adobe XD or Photoshop. Strongest is collaboration and handoff, scored 7–8: inspect panels auto-generate measurements, assets and platform-tailored code snippets, Connected Components link finalized designs to codebase components, and a documented API with webhooks and integrations including Jira, Storybook, VS Code, Slack and Microsoft Teams. Design and prototyping clusters at 6–7 — global styleguides with parent-child inheritance and JSON design tokens are credited, but we found no public information on a drawing canvas or interactive prototyping. AI and content rights, at 6–7, has unusually plain terms: no training on Customer Data, third-party AI providers contractually barred from training, opt-in features, input and output are Customer Data. Weakest is sovereignty at 0–1: Zeplin, Inc. under California law, data transferred to the United States, personal information may be stored anywhere in the world on Amazon Web Services. Brand asset governance sits at 3–4 and file ownership and portability at 4; no criterion splits by more than a point. On pricing, the captured pages show only "Try for free today".
Speaks for it
- Collaboration and handoff scores 7–8 on inspect panels that auto-generate measurements, assets and platform-tailored code snippets.
- Connected Components link finalized designs to components in the codebase, with code snippets visible during inspection.
- A documented API with webhooks and buildable extensions sits alongside named Jira, Azure DevOps, Storybook, GitHub, VS Code, Slack and Microsoft Teams integrations.
- The AI terms exclude training on Customer Data, contractually bar third-party AI providers from training, keep the features opt-in and treat input and output as the customer's Customer Data.
- Global styleguides with parent-child inheritance hold components, colors, text styles and spacing tokens exportable as JSON, with version diff between published versions.
Held against it
- Sovereignty scores 0–1: the contracting entity is Zeplin, Inc. under California law, data is transferred to the United States, and personal information may be stored anywhere in the world on Amazon Web Services.
- We found no public information on whether guests or reviewers can comment without a paid seat.
- We found no public information on exporting whole projects with their structure or on what happens to files after a downgrade or cancelled contract.
- Brand asset governance scores 3–4, with no public information on locked templates, guidelines published in the tool, or rights and expiry metadata on assets.
- We found no public information on the AI model providers, where AI processing runs, an admin control to switch AI off for an organisation, or any IP indemnity.
Best for
- You hand off finalized designs from Figma, Sketch, Adobe XD or Photoshop to developers who need measurements, assets and platform-tailored code snippets.
- You manage a design system across projects through global styleguides with inheritance and want design tokens exported as JSON.
- You want AI terms in writing: no training on Customer Data, opt-in features, input and output as your Customer Data.
- Your developers work in Jira, Azure DevOps, Storybook, VS Code, Slack or Teams and you want a documented API with webhooks.
Avoid if
- You require EU residency or a European contracting entity — the captured pages show Zeplin, Inc. under California law, transfer of data to the United States, and storage anywhere in the world on Amazon Web Services.
- You need to draw or prototype inside the tool — the documented workflow is publishing in frames made in Figma, Sketch, Adobe XD or Photoshop.
- Your non-designers need locked brand templates or licence and expiry metadata on assets — the documented styleguides hold components, colors, text styles and spacing tokens.
- You need to export whole projects with their structure — the documented exports are design tokens as JSON and React Native code snippets.
The scores
| Criterion | Panel median |
|---|---|
| Design, prototyping & design systems | 3 of 5 |
| Collaboration, review & developer handoff | 3.5 of 5 |
| Brand assets & governance | 2 of 5 |
| Files, formats & portability | 2 of 5 |
| AI features & rights to the work | 3 of 5 |
| European sovereignty | 0.5 of 5 |
Design, prototyping & design systems
Show reasoningHide reasoning
How this is scored
The making itself: vector and layout tools, interactive prototypes, and the shared components, styles and tokens that keep a company's products and materials consistent — judged on what the feature and help pages document, not on showcase images.
0 — Not a design tool: a file viewer, a stock library or a single-purpose converter in which nothing is laid out or drawn.
3 — A canvas or editor with templates, shapes, text and images; reusable components, shared styles and prototyping are basic or not described.
5 — Reusable components or styles shared across files, responsive or auto layout, and clickable prototypes or presentations linking screens.
8 — A design system managed in the tool: team libraries that update where they are used, variables or tokens for colour, type and spacing with modes or themes, component variants and properties, prototypes with transitions and conditional logic, and library changes published with versions.
10 — The design system is a governed product: library releases versioned and reviewable, token export in a documented format for development, usage analytics per component, and accessibility checks such as contrast built into the editor.
The Product Designer
Zeplin manages a design system rather than hosting one being drawn: global styleguides with parent-child inheritance share components, colors, text styles and spacing across projects, variants arrive auto-organized by type and state and collapse into one cycleable component, and version history with a visual diff makes changes reviewable. Design tokens are generated from any design tool and export as JSON. We found no public information on vector or layout tools or interactive prototypes — the captured pages describe publishing and organizing designs made in Figma, Sketch, Adobe XD and Photoshop. 1 3 4 6 8 9
The Frontend Engineer
Nothing is drawn in Zeplin — frames are published in from Figma, Sketch, XD or Photoshop — but the design-system half is real: global styleguides with parent/child inheritance, colour, text-style and spacing tokens exportable as JSON, and component variants that collapse into one component developers can cycle through, with version diff between published versions. What keeps it below the top band is the making itself: we found no public information on prototypes with transitions or conditional logic. 3 4 6 9
The Brand Marketer
Zeplin is where designs land, not where they are made: frames are published in from Figma, Sketch, Adobe XD or Photoshop, and I found no public information on drawing, layout authoring or prototyping inside the tool itself. The design-system half is real, though — global styleguides with parent/child inheritance, colour, text-style and spacing tokens exportable as JSON, component and screen variants, and Version Diff to see what changed between versions. 1 3 4 6 9
The Agency Owner
The captured pages describe a tool you publish into rather than draw in — frames come from Figma, Sketch, Adobe XD and Photoshop — and we found no public information on prototyping or clickable flows. The design-system half is genuinely strong: local and global styleguides with parent/child inheritance, components, colours, text styles and spacing tokens managed centrally with version history and diffing, component and screen variants organised by state, and design tokens generated from any tool. That places it above a basic component library but short of a fully governed in-tool design system, since token modes or themes are not described. 1 3 4 6 8 9
The Data Protection Officer
The design system is genuinely managed in the product: global styleguides with parent and child inheritance hold components, text styles, colours and spacing tokens, tokens export as JSON, and component and screen variants collapse into single items with cycleable states and version comparison. We found no public information on a drawing canvas or interactive prototypes — designs are published in from Figma, Sketch, Adobe XD and Photoshop — nor on token themes or modes. 3 4 6 8 9
The Skeptic
Designs are published in by plugin from Figma, Sketch, Adobe XD and Photoshop; the captured pages describe no drawing canvas, so the making itself is imported. What is documented is genuine design-system management: global styleguides with parent-child inheritance, variants collapsed into one component with cycleable states, and colour, text-style and spacing tokens generated from any tool and exportable as JSON, with version diff. We found no public information on interactive prototyping, prototypes with transitions and logic, or token themes and modes. 1 3 4 6 9
Collaboration, review & developer handoff
Show reasoningHide reasoning
How this is scored
Working on the same files with colleagues, clients and developers: comments and review, permissions for internal and external people, and the handoff that gives engineering measurements, assets and code rather than screenshots.
0 — A single-user tool: files are worked on alone and passed on as exports.
3 — Files shared by link with comments or real-time co-editing; guest access, permissions and a developer view are basic or not described.
5 — Real-time co-editing, comments with mentions, sharing with view or edit rights per file or project, and an inspect or developer view with measurements and asset export.
8 — Guests and reviewers who comment without a paid seat, version history with restore, branching or review of changes before they reach the main file, a developer mode that links components to code, a documented API and plugins, and named integrations with issue trackers and code tools.
10 — Handoff is a contract between design and code: component properties mapped to code components, token and asset export automated through the API, an audit log of access and sharing, and external access governed by domain, expiry and admin policy.
The Product Designer
Handoff is the product: inspection generates measurements, assets and platform-tailored code snippets, Connected Components link finalized designs to codebase components with snippets visible at inspection, and comments and annotations carry GIFs, product requirements and API endpoints. A documented API with webhooks, buildable extensions, and named integrations with Jira, Azure DevOps, Storybook, VS Code, Slack and Microsoft Teams are all captured. We found no public information on guests or reviewers commenting without a paid seat. 1 6 8
The Frontend Engineer
The inspect panel auto-generates measurements, assets and code snippets, and Connected Components genuinely map design components to the ones in the codebase, with Storybook and GitHub links and snippets visible during inspection. There is a documented API with webhooks, buildable extensions, and named Jira, Azure DevOps and VS Code integrations, plus version diff between published versions. I hold it below the top band because I found no public information on whether guests and reviewers can comment without a paid seat, on restoring versions, or on any access audit log. 1 6 8 9
The Brand Marketer
Handoff is the whole product: auto-generated measurements, assets and code snippets in the inspect panel, Connected Components tying finalized designs to the codebase with code snippets visible on inspection, a documented API with webhooks, and named integrations with Jira, Azure DevOps, VS Code, Slack, Microsoft Teams, Storybook and GitHub. Comments and annotations with product-requirements pinning are documented too, but I found no public information on guests or reviewers commenting without a paid seat, on restoring from version history, or on branching or review before changes go live. 1 3 4 6 8
The Agency Owner
Handoff is the product's spine: measurements, assets and platform-tailored code snippets appear on inspect, comments and annotations cover requirements and API endpoints, and Connected Components tie finalized designs to real components in the codebase with snippets visible during inspection. A documented API with webhooks, buildable and community extensions, Storybook linking, and named integrations with Jira, Azure DevOps, VS Code, Slack, Microsoft Teams and Zapier are all published. We found no public information on clients or guests commenting without a paid seat, on restoring a prior version, or on an access audit log. 1 3 6 8 10
The Data Protection Officer
Handoff is the product: inspection auto-generates measurements, assets and platform-tailored code snippets, connected components link finalised designs to the codebase with snippets shown during inspection, and Jira, Azure DevOps, Storybook, GitHub, VS Code, Slack and Teams are named alongside a documented API, webhooks and buildable extensions. We found no public information on guests or reviewers commenting without a paid seat, on restoring versions, or on an audit log of access and sharing. 1 3 6 8
The Skeptic
Handoff is the core of the product: the inspect panel auto-generates measurements, assets and platform-tailored code snippets, Connected Components links finalised designs to components in the codebase, and Storybook, GitHub, Jira, Azure DevOps and VS Code are named alongside a documented API, webhooks and a buildable extension platform, with comments, annotations, version history and version diff. We found no public information on guests or reviewers who comment without a paid seat — the reviewer-into-billed-editor question is not answered anywhere — nor on restoring or branching versions or an audit log. 1 4 6 8
Brand assets & governance
Show reasoningHide reasoning
How this is scored
Keeping a brand usable and correct across a company: a central library for logos, images and templates, brand guidelines people can find, locked templates that let non-designers produce material, and rights and expiry metadata on every licensed asset.
0 — No shared assets of any kind; the product has no library, kit or template that a team uses together.
3 — A shared folder, brand kit or template set with logos, colours and fonts; locking, guidelines and asset metadata are basic or not described.
5 — A central brand kit or library with logos, colours and fonts, team templates that non-designers can fill, and the ability to lock brand elements or restrict who edits templates.
8 — Brand guidelines published in the tool, tagging and search across assets, approval workflows for new assets and template output, version control on assets, rights, usage and expiry metadata with warnings on expiry, and access per team, market or partner.
10 — Brand governance is auditable: every asset carries its licence, owner and permitted use, usage of each asset is tracked across files and channels, distribution to external partners is logged, and the whole library with metadata is exportable in a documented format.
The Product Designer
Styleguides act as a shared kit — components, colors, text styles and a spacing system centralized with parent-child inheritance across teams. We found no public information on logos and image libraries, locked templates non-designers can fill, published brand guidelines, or rights and expiry metadata on licensed assets. 4 6 8
The Frontend Engineer
Styleguides are a real shared library — components, colours, text styles and spacing held centrally with parent/child inheritance across projects — but that is a design-system library rather than a brand asset one. We found no public information on logos, fonts, locked templates non-designers can fill, or rights and expiry metadata on assets. 4 6 8
The Brand Marketer
A centralised styleguide holding colours, text styles, spacing and components, with parent/child inheritance across projects, is a proper brand-kit core and would help me keep twelve offices on one truth. But for my actual people — non-designers in sales offices — I found no public information on templates they can fill, on locking brand elements, on guidelines published inside the tool, or on licence, rights and expiry metadata for any asset, so this stays at kit level rather than governance. 4 6 8
The Agency Owner
Styleguides provide a centralized, inheritable library of components, colours, text styles and spacing tokens with version control — the raw material of brand consistency across projects. But the governance layer is undemonstrated: we found no public information on brand guidelines published in the tool, locked templates non-designers can fill, approval workflows, or licence, usage and expiry metadata on assets. 4 6 8
The Data Protection Officer
Styleguides give a team one central library of components, colours, text styles and spacing tokens that can inherit across projects, which is a real shared library rather than a folder. We found no public information on locking brand elements, guidelines published in the tool, approval workflows, or rights and expiry metadata on assets. 4 6 8
The Skeptic
Styleguides serve as the central library: components, colours, text styles and spacing shared across projects with parent-child inheritance and centralised updates — a shared design-language kit rather than brand governance. We found no public information on a logo or image library, brand guidelines published in the tool, locked templates non-designers can fill, or rights and expiry metadata on licensed assets. 4 6 8
Files, formats & portability
Show reasoningHide reasoning
How this is scored
Whether the work can leave: open or documented file formats, export that keeps layers, vectors and components, offline or self-hosted options, and what happens to files after a downgrade, a removed seat or a cancelled contract.
0 — Work cannot leave the product: no export or download of designs is offered.
3 — Export of designs as images or PDF per page or frame; export of whole files with structure and access after cancellation are basic or not described.
5 — Export to PNG, PDF and SVG with vectors and text kept, whole files downloadable to a local copy, and files of a downgraded or cancelled account addressed in the help centre or terms.
8 — An open or publicly documented file format, import from and export to other named tools documented, bulk export of a team’s files, an API that reads full file structure, files of removed users transferred to the organisation by policy, and a stated retention and deletion timeline after the contract ends.
10 — Portability is built in: an open-source or openly specified format, self-hosting or a local-first option, round-trip export without loss of components and prototypes, and the customer’s ownership of all files and their export rights written into the terms.
The Product Designer
Design tokens export as JSON — a zip package, individual files per token type, clipboard copy, or fetched through the API — and React Native code snippets export across platforms, which is real structured portability of the system. We found no public information on exporting whole projects with their structure, offline or self-hosted options, or what happens to files after a downgrade or cancelled contract. 6 9 10
The Frontend Engineer
Tokens leave in a documented JSON form — a zip package, individual files for colour, text-style and spacing, or a fetch through the API — and React Native code snippets export across platforms, which is more than screenshot handoff. But we found no public information on exporting whole projects with structure, on a documented file format, or on what happens to files after a downgrade or cancelled account. The Mac and Windows apps appear as downloads; we found no public information on offline or self-hosted options. 1 6 9 10
The Brand Marketer
Design tokens can be exported as a zip package or individual JSON files for colour, text-style and spacing, React Native code snippets can be generated from layers, colours and text styles, and an API accesses the data in Zeplin. I found no public information on downloading whole files with their structure, on exporting screens as images or PDF, or on what happens to files after a downgrade or a cancelled contract. 6 9 10
The Agency Owner
Structured export exists but is narrow: design tokens export as a JSON zip package, a clipboard copy, or individual files for colours, text styles and spacing, React Native snippets export by extension, and the API reads the data in Zeplin. We found no public information on downloading whole project files with their structure, or on what happens to a client's work after a downgrade or cancelled contract — the first question I ask before committing an agency project to any tool. 6 9 10
The Data Protection Officer
Tokens leave in a documented JSON package by download, clipboard copy or API fetch, code snippets generate for named platforms, and import from Figma, Sketch, Adobe XD and Photoshop is documented, with Mac and Windows desktop apps offered. We found no public information on exporting whole designs or files with structure, a documented file format, or what happens to files after a downgrade or a cancelled contract. 3 6 9 10
The Skeptic
What can leave is narrow but structured: colour, text-style and spacing tokens export as a.zip package, individual JSON files, a clipboard copy or through the API, and React Native code snippets export across platforms. We found no public information on exporting screens or whole projects with their structure, on an open or documented file format, or on what happens to files after a downgrade, a removed seat or a cancelled contract. 1 9 10
AI features & rights to the work
Show reasoningHide reasoning
How this is scored
What the vendor's AI does with the customer's files and what the customer may do with the AI's output: training on customer content and the opt-out, the models and where they run, commercial use of generated images, stock licences and indemnity.
0 — The terms state that customer files train the vendor’s models with no opt-out, or that generated output may not be used commercially.
3 — AI features described on an AI or help page with a general statement on responsible use or data handling; training on customer files, admin controls and output rights are basic or not described.
5 — A statement on whether customer content trains the models (excluded, or with a documented opt-out), AI features that an admin can switch off for the organisation, and commercial use of generated output addressed in the terms or AI page.
8 — Training excluded by default for business plans, model providers and the processing location of AI features stated, generated content labelled or carrying content credentials, stock and template licences stated per asset type, and an IP indemnity for generated output on a named plan.
10 — AI is governed in writing: a per-feature list of models, providers and locations, admin controls per team and feature, a log of AI use, training exclusion and output ownership in the contract terms, and indemnity and licence limits published in full.
The Product Designer
The AI terms are unusually explicit: Zeplin does not use Customer Data to train its models, third-party AI providers are contractually barred from training on input or output, features are opt-in, AI input and output are the customer's own data, and model improvement happens only on explicit permission or feedback. We found no public information on the models, providers and processing locations behind the features, an organisation-level admin switch, labelling of generated content, or any IP indemnity for output. 11 12 2
The Frontend Engineer
The AI terms are unusually clear: Zeplin does not use customer data to train its models, third-party AI providers are contractually barred from training on input or output, and input and output remain the customer's data. The features are opt-in — design review that catches layout issues and token mismatches, and screen organising, with custom prompts — though the terms disclose output is not verified and may not be unique. We found no public information on named model providers or processing locations, organisation-wide admin switches, content credentials, or indemnity. 2 11 12
The Brand Marketer
The AI terms answer my trade-fair question in writing: Zeplin does not use Customer Data to train its models, third-party AI providers are contractually barred from training on input or output, the features are opt-in, and Input and Output are the customer's own Customer Data — and since Zeplin AI reviews designs and organises screens rather than making images, there is no generated-image risk to clear. I found no public information on organisation-level admin controls, on the models and providers behind the features and where they run, or on any indemnity; the terms themselves note output may not be unique and is not verified by Zeplin. 11 12
The Agency Owner
The AI terms are unusually clean for an agency handing over client work: Zeplin states it does not use Customer Data to train its AI models, third-party AI providers are contractually barred from training, Input and Output are the customer's Customer Data, and any training happens only on voluntarily given feedback or explicit permission. We found no public information on the model providers or processing locations behind Zeplin AI, admin-level switches for an organisation, or an IP indemnity, and the terms note output may not be unique and is not verified by Zeplin. 11 12
The Data Protection Officer
The AI terms are the best-governed part of the record: training on customer data is excluded outright in the terms and third-party model providers are contractually barred from training or improving their models on input or output, the features are opt-in, and input and output remain the customer's own data. We found no public information on the model providers or the processing location of the AI features, on an organisation-wide admin switch, on content credentials for generated output, or on any indemnity. 2 11 12
The Skeptic
The AI terms are unusually plain: no training of the models on Customer Data, third-party AI providers contractually barred from training, features strictly opt-in, and input and output treated as the customer's Customer Data. But we found no public information on admin controls to switch AI off for an organisation, on model providers or processing locations, or on an IP indemnity for generated output — and the terms themselves warn output may not be unique and exclude third-party AI downtime from the uptime calculation. 2 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where design files, brand assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline.
0 — Proven non-EU on every dimension the evidence covers: non-EU contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven: an EU contracting entity or EU representative, EU data residency (even if only on an enterprise plan), or a published DPA, with the rest of the chain unstated.
5 — EU hosting stated for files as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (AI, rendering, support) is unstated or partly non-EU.
8 — EU contracting entity, files, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and the processing location of AI features stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Product Designer
The captured pages prove a non-EU posture on every dimension they cover: Zeplin, Inc. under California law, data transferred to the United States, hosting on Amazon Web Services with storage anywhere in the world, and no EU residency option stated. EU Standard Contractual Clauses for transfers to the US and a referenced subprocessor list are the only European-facing elements; we found no public information on an EU entity, EU hosting, or certifications. 2 11
The Frontend Engineer
Zeplin, Inc. is the contracting entity under California law, and the policy states plainly that using the services transfers data to the United States, where personal information may be stored anywhere in the world on Amazon Web Services. EU transfers rest on standard contractual clauses rather than an EU entity, EU hosting option or stated EU residency — every sovereignty dimension the captured pages cover points to the US. 2 11
The Brand Marketer
The contracting entity is Zeplin, Inc. governed by California law, the service transfers data to the United States, and personal information may be stored anywhere in the world on Amazon Web Services; I found no public information on a committed EU hosting option. The only European-facing elements I can point to are the EU Standard Contractual Clauses governing transfers and a published subprocessor list. 2 11
The Agency Owner
The contracting entity is Zeplin, Inc. under California law, processing runs on Amazon Web Services, and the privacy policy states plainly that using the service transfers data to the United States, with EU-to-US transfers governed by the 2021 standard contractual clauses. Storage is described as possibly anywhere in the world, including the EU, but as an outcome rather than a commitment, and we found no public information on an EU hosting option. A subprocessor list URL is published, which is the one governance gesture here. 2 11
The Data Protection Officer
The contracting entity is Zeplin, Inc. under California law, and the privacy policy states data is transferred to the United States and may be stored anywhere in the world, including the United States and the European Union, on Amazon Web Services — a storage statement that commits to no European region. EU-to-US transfers rest on the 2021 standard contractual clauses, a subprocessor list is published, and we found no public information on a European entity or a selectable EU hosting option. 2 11
The Skeptic
The contracting entity is Zeplin, Inc. under California law, processing runs on Amazon Web Services, and the privacy policy states data may be stored anywhere in the world and will be transferred to the United States under the EU's 2021 standard contractual clauses. A subprocessor list is published and a DPA is referenced for AI processing, but we found no public information on an EU entity, EU hosting as a stated option, or EU residency for design files. 2 11
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual cost for their team from public pages alone — which seat types exist and what each may do, how viewers and guests are billed, how seats are added and trued up, AI credits, and the plan where SSO, admin controls and brand features begin.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price or one priced plan, per seat or flat.
5 — Per-seat prices public for the main plans with the billing period stated and the main features per plan listed.
8 — Every plan and seat type priced, free viewers and guests stated with their limits, how and when added seats are billed explained, AI credits and storage priced or included explicitly, the plan that unlocks SSO and admin controls named, and VAT treatment stated.
10 — Complete cost computability: annual cost derivable for a given mix of editors, viewers and guests, true-up and auto-upgrade rules published, every add-on priced publicly, and contract term, renewal and downgrade conditions stated.
The Product Designer
The only pricing information across the captured pages is a free trial offer. We found no public information on plan prices, seat types, viewer or guest billing, or the plan where SSO and admin controls begin, so a buyer cannot compute a cost from these pages. 4
The Frontend Engineer
The only pricing signal on the captured pages is "Try for free today". We found no public information on plan prices, seat types, how viewers or guests are billed, true-ups, VAT treatment, or which plan unlocks SSO — a buyer cannot compute an annual cost from these pages. 4
The Brand Marketer
The captured pages show only a "Try for free today" offer and payment processed through Stripe; I found no public information on seat prices, plan tiers, how viewers or guests are billed, where single sign-on and admin controls begin, or VAT treatment. A buyer cannot begin to compute an annual team cost from what was captured. 2 4
The Agency Owner
The only pricing-related statement on the captured pages is "Try for free today" — we found no public information on plan names or per-seat figures, how viewers or guests are billed, AI credit pricing, where SSO and admin controls begin, or VAT treatment. A buyer cannot begin to compute an annual team cost from public pages. 4
The Data Protection Officer
The only pricing information we found is a free-trial invitation on the design system page. We found no public information on prices for any paid plan, on seat or viewer billing, or on which plan unlocks single sign-on and admin controls. 4
The Skeptic
The only pricing fact on the captured pages is "Try for free today". We found no public information on plan names, per-seat prices, billing periods, how viewers or guests are billed, seat true-ups, or the plan where SSO and admin controls begin — a buyer cannot compute an annual team cost from these pages. 1 4
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Zeplin
Is Zeplin European?
Not determined: the vendor’s pages as captured do not say where Zeplin is based.
Where does Zeplin store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Zeplin have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Zeplin?
As of 4 Nov 2026, the panel rates Penpot (3.5/5), Sketch (3/5) and Collaboard (3/5) highest among the other 21 Design products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Penpot (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Zeplin alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 15 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page zeplin.io Checked 3 Nov 2026 Details →
- 2 Privacy policy — found from the homepage zeplin.io Checked 3 Nov 2026 Details →
- 3 Design, prototyping & design systems — found from sitemap zeplin.io Checked 3 Nov 2026 Details →
- 4 Design, prototyping & design systems — found from sitemap zeplin.io Checked 3 Nov 2026 Details →
- 5 Collaboration, review & developer handoff — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 6 Collaboration, review & developer handoff — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 7 Brand assets & governance — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 8 Brand assets & governance — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 9 Files, formats & portability — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 10 Files, formats & portability — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →
- 11 AI features & rights to the work — found from sitemap zeplin.io Checked 3 Nov 2026 Details →
- 12 AI features & rights to the work — found from sitemap support.zeplin.io Checked 3 Nov 2026 Details →