Simplify your WordPress workflow!
Build faster, cleaner, and more reliable WordPress websites using lightweight plugins designed for real-world workflows.
Get started nowAdvanced settings
Overview
The Advanced tab holds two deterrents aimed at visitors who try developer tools instead of right-click. Both are free. The PRO section on the same tab is described in Fine-grained control.
Block view-source shortcuts
Block view-source shortcuts (Ctrl/⌘+U, F12, Ctrl+Shift+I/J/C)
Intercepts the keyboard shortcuts that open the page source and the browser’s developer tools.
This is best-effort only. Browsers do not let a page block their own menus, so a visitor can still open the source from the browser menu or with a view-source: address. Treat it as a speed bump for casual visitors, not a lock.
DevTools indicator
Show the message if DevTools appears to be open
Shows your protection message when the developer tools seem to be open. Detection is based on an unusually large gap between the window and the page size, which often — but not always — means DevTools is docked open. It can misfire on some window managers, or when the browser window is resized in an unusual way.
The free plugin only shows the message. With PRO you can instead blur the page or redirect the visitor — see DevTools reaction.
When to use these options
- Turn them on for sites where casual visitors regularly try to grab content — photography, recipes, course material.
- Leave them off where your audience is developers, or where false alarms would bother legitimate readers.
- Exempt roles are never affected, so you can keep working with DevTools on your own site while logged in.
