Framer
Security Guide

How to Secure Your Framer App

Last updated: January 12, 2026

Framer enables visual website building with code capabilities. This guide covers securing your Framer sites.

Step-by-Step Security Guide

1. Secure Code Overrides

Code overrides run client-side. Never include API keys or secrets in override code.

2. Use External APIs Securely

For API calls requiring secrets, use serverless functions. Framer code is visible to users.

3. Audit Third-Party Scripts

Review any scripts added via custom code embeds. They have access to your page.

4. Configure CMS Security

Review CMS collection visibility. Ensure sensitive content isn't exposed unintentionally.

5. Enable Form Spam Protection

Use Framer's built-in form features with spam protection, or integrate a secure form backend.

6. Verify HTTPS Configuration

Ensure SSL is properly configured for custom domains.

Common Security Mistakes

Avoid these common Framer security pitfalls:

API keys in code overrides
Sensitive API calls from client-side
Unvetted third-party scripts
CMS content visibility not configured
Forms without spam protection

Recommended Security Tools

Use these tools to maintain security throughout development:

VAS Security Scanner
npm audit / yarn audit
Git-secrets
Snyk

Ready to Secure Your App?

Security is an ongoing process, not a one-time checklist. After implementing these steps, use VAS to verify your Framer app is secure before launch, and consider regular scans as you add new features.

Frequently Asked Questions

Can users see my Framer code overrides?

Yes, code overrides run in the browser and are visible in developer tools. Never include secrets. Use serverless functions for secure API calls.

Is Framer CMS secure?

Framer CMS is secure, but you control visibility settings. Review collection settings to ensure sensitive content is properly restricted.