Platform Fonts vs Your Uploads
On Wix and Squarespace, typography usually comes from two buckets:
- Platform / partner fonts offered in the editor
- Custom fonts you upload (or add via custom code)
These buckets have different legal stories.
Fonts Provided by the Platform
When you pick a font from the builder's built-in library, the platform generally has arrangements that let you use that font inside their product on sites hosted there.
That does not automatically mean you can:
- Download the font files for use in print, apps, or a custom Next.js rebuild
- Move the same files to Shopify, WordPress, or a self-hosted stack
- Assume perpetual rights if you leave the platform
If you migrate off Wix or Squarespace, re-license (or replace) every commercial family.
Custom Uploaded Fonts
If you upload .ttf / .woff files — or inject @font-face via custom code — you are responsible for the web license.
Common failure modes:
- Uploading desktop fonts from a personal Adobe Fonts sync folder
- Using a client's brand font without a web add-on
- Buying a single-seat desktop license and uploading it to a live storefront
The platform hosting your site does not indemnify unlicensed uploads.
Adobe Fonts and Builders
Some templates and workflows encourage Adobe Fonts. Confirm:
- The Adobe Fonts web project is active
- Self-hosting extracted files is not happening on the side
- Your plan covers the site's use case
Practical Checklist for Builder Sites
- List every non-system font used in the theme
- Mark each as platform-provided or custom upload
- For uploads: store the invoice / EULA in your drive
- Before a platform migration: plan font replacements
- After publishing: scan the live URL for unexpected font files
Conclusion
Wix and Squarespace simplify design; they do not erase font copyright. Built-in fonts are for use on the platform. Everything you upload needs its own web rights.