---
schema_version: "1"
id: 5d0ade00acbb33af363dcd1c1e98ab61713cb997f3371a9295d8883a1198f22f
title: What Does Lightning Locker Affect?
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/lwc/lightning-components-security/guides/locker/locker-where.md
canonical_url: https://developer.salesforce.com/docs/platform/lightning-components-security/guide/locker-where.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d796e89bb6cb1d74a43e8befcb3ae19c5178047cb628b4a38bcff3ad7ccd967a
products:
  - Security for Lightning Components
  - lwc
---
# What Does Lightning Locker Affect?

Find out what’s affected and what’s not affected by Lightning Locker.
Lightning Locker enforces security and best practices for custom Lightning components you use in:

- Lightning Experience
- Salesforce mobile app
- Experience Builder sites
- Flows
- Standalone apps that you create (for example, myApp.app) to run in Salesforce Classic or Lightning Experience
- Any other app where you can add a custom Lightning component, such as Salesforce Console in Lightning Experience
- Lightning Out
- Visualforce pages in Salesforce Classic
- Visualforce-based sites

Lightning Locker doesn’t affect environments where you don’t use custom Lightning components.