Free tools Windows power users keep installed
One-click scans. No signup required.
You cannot reliably stop visitors from capturing a public website. JavaScript can add friction, and managed browsers or protected video platforms can impose stronger controls in specific environments, but no website setting can disable every operating-system shortcut, app, browser feature, or camera. Choose a measure based on what you need to protect; do not treat a blocked key or a darkened page as security.
What can a website actually control?
A webpage controls its own content and can ask the browser to handle that content in certain ways. It does not control the visitor’s device. A person can use an operating-system screenshot shortcut, a different browser or application, a browser feature outside the page’s JavaScript, or a camera pointed at the display. Some capture methods may also happen without a page event that your script can observe.
That makes the threat model important. If the goal is to discourage casual copying of an image, friction or a visible notice may be worthwhile. If the goal is to protect paid video, use authenticated delivery and platform-supported content protection, and plan for compatibility limits and leaks. If your users are on devices managed by your organization, administrator-enforced browser policies may offer stronger controls than a public site can.
- Deterrence can discourage casual actions but is easy to bypass.
- Page-level restrictions can limit a specific browser API, not the device’s general screenshot function.
- Managed-device policies can control supported capture paths in enrolled browsers, subject to platform and policy limits.
- DRM and watermarking can raise the effort of copying premium media and help attribute leaks, but cannot guarantee that no copy can be made.
Can JavaScript block Print Screen or screen recording?
No—not reliably. A page can listen for a keydown event and try to suppress a key such as Print Screen. It can also disable the context menu or interfere with copy, drag, or print interactions. These actions only affect events that reach the page and can be bypassed with another capture path, a modified browser, or a camera. Do not claim that a script detects every screenshot or stops screen recording in Chrome.
Optional friction for casual copying
This example suppresses the context menu and attempts to intercept common print and screenshot keys. It is a deterrent, not a security boundary. Browser and operating-system behavior varies, and users can bypass it. Use it only when the added inconvenience is acceptable for your audience.
document.addEventListener('contextmenu', (event) => {
event.preventDefault();
});
document.addEventListener('keydown', (event) => {
const key = event.key.toLowerCase();
const printScreen = event.key === 'PrintScreen';
const printCommand = (event.ctrlKey || event.metaKey) && key === 'p';
if (printScreen || printCommand) {
event.preventDefault();
}
});Put the script in a JavaScript file loaded by the page or in a script block after the relevant document content. Test with the browsers and assistive technologies your site supports. Suppressing context menus and keyboard shortcuts can interfere with ordinary tasks, accessibility workflows, and user expectations. Avoid disabling selection or copying across an entire site unless that trade-off is intentional; it can make legitimate reading and use harder without meaningfully protecting the content.
What does the display-capture Permissions Policy do?
The display-capture Permissions Policy governs whether a document can initiate screen capture through the Screen Capture API’s getDisplayMedia() method. It does not disable a visitor’s normal screenshot shortcut, a separate screen-recording application, or a camera. MDN says that when this directive is disabled for a document, a call to getDisplayMedia() throws a NotAllowedError. MDN labels support limited and experimental and lists the page as last modified July 4, 2025.
To deny the capability to documents delivered with your response, configure this HTTP response header on the server:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Permissions-Policy: display-capture=()Configure the header in the web server, hosting platform, or reverse proxy that sends the page; placing the text in the page body does nothing. Verify the response in your browser’s network tools and test the browser versions relevant to your audience. This restriction is useful when you do not want your own page or embedded documents to initiate capture through that API. It is not an anti-screenshot header.
Does Content Security Policy prevent screenshots?
No. Content Security Policy (CSP) controls which scripts and other resources a document may load, and is primarily a defense against risks such as cross-site scripting. It does not disable screenshots or screen recording. MDN describes CSP as a feature that helps prevent or minimize certain security threats. Use it to set a resource-loading policy, not as a substitute for content-protection controls.
Rank #3
- 【Tired of constantly searching for or resetting your passwords?】 MOSA BEAR password keeper book is the perfect solution for you! This password book provides a dedicated place to securely store all your important website addresses, emails, usernames and passwords, ensuring your information is protected and easy to find. The well-designed log pages help you manage multiple accounts in a systematic way, saying goodbye to password confusion.
- 【Premium Design & Password Security】 The password book with alphabetical tabs features an anonymous cover design with no title on the cover, effectively avoiding information exposure. The password keeper design is specifically designed with password security in mind, providing space to record password hints instead of writing directly on the password itself, further protecting your important information.
- 【Simple Layout and Plenty of Space】The 160-page password logbook is designed to provide ample space to record passwords and other important information. It can store up to 414 passwords. In addition, it provides extra pages to record other information, such as email setup, card information, computer operating system information, software licenses, and more. The journal also includes 3 blank pages at the end for you to add additional notes.
- 【Palm-sized Size & Premium Quality】 This password notebook has an ideal size, 4.3" x 5.7", for carrying around, whether in a purse or pocket. Its sturdy glue binding allows the notebook to unfold smoothly and is more comfortable to use. The inner pages are made of high-quality 100GSM thick paper, which can effectively reduce ink penetration and ensure a cleaner and neater writing effect. The overall design takes into account both portability and durability, making it an ideal choice for recording important passwords.
- 【A-Z Tabs for Quick Search 】Our password book comes with alphabetical tabs to help you find the password you need quickly and easily. Alphabetically organized tabs ensure that you can quickly flip to the right section, saving you the time and hassle of searching for your password.
What can managed browsers enforce?
Organizations that enroll and manage devices have options unavailable to an ordinary public website. These policies are applied by administrators to managed browsers or users; a site visitor cannot be made subject to them simply by adding JavaScript to a page. Their scope and effectiveness depend on the product, license, operating system, and capture method.
Chrome Enterprise
Chrome Enterprise documents screenshot prevention for managed users and browsers with a Chrome Enterprise Premium license. Its controls can apply to keyboard-shortcut screenshots and to apps or extensions that use Chrome’s capture API. Administrators can define URL exceptions. Google’s documentation lists Android, ChromeOS, iOS, and Chrome on Windows, macOS, and Linux, while also specifying platform differences for screenshot and screen-share prevention. Check the current administrator documentation and your organization’s license and device configuration before relying on a particular platform behavior.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Microsoft Edge
Microsoft Edge provides a managed-device policy named DisableScreenshots. Microsoft Learn lists support beginning with Edge 77 on Windows and macOS, Edge 146 on Android, and no support on iOS; that policy page was last updated September 11, 2026. When enabled, the policy blocks keyboard shortcuts and extension APIs. Microsoft cautions that Web Capture within the browser, operating-system features, or other applications may still capture content. This is an administrator control for managed environments, not a universal switch a website can turn on.
Rank #4
- Bookbound planner helps you keep track of passwords and favorite websites
- Room for over 200 entries; 3.5 x 6 inch page sizes
- User name and security questions field
- Tips for what makes a strong password; web resources; notes pages
- Printed on quality paper containing 30% post-consumer waste; black simulated leather cover; 3.63 x 6.13 x .21 inches
| Approach | What it can do | Important limit |
|---|---|---|
| JavaScript deterrents | Suppress some page-level key, menu, copy, drag, or print interactions. | Easy to bypass; does not control capture methods outside the page. |
display-capture policy |
Prevent a document from initiating capture with getDisplayMedia(). |
Does not block ordinary screenshots; support is limited and experimental per MDN. |
| Chrome Enterprise Premium | Administer capture restrictions for managed users and browsers on documented platforms. | Requires the managed environment and applicable license; behavior differs by platform and capture path. |
Edge DisableScreenshots |
Block keyboard shortcuts and extension APIs in supported managed Edge environments. | Web Capture and methods outside the browser may still work; iOS is listed as unsupported. |
How should you protect paid video or premium media?
For valuable video, use layered delivery rather than relying on a website script. Authenticate access, use platform DRM where supported, deliver through secure playback paths, use short-lived URLs where appropriate, and consider visible or forensic watermarks. These measures raise the cost of casual copying and can help identify the account or session associated with a redistributed copy.
DRM behavior is platform-dependent: capture blocking can differ across Windows, macOS, Linux, Android, and iOS, as well as by browser and hardware combination. A playback path that resists capture on one device may behave differently on another. Watermarks and overlays can deter sharing or support leak attribution, but a determined viewer can still film the screen. Test the actual device, browser, and playback combinations your customers use, and describe protection as risk reduction rather than guaranteed prevention.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which approach should you choose?
- For casual copying of ordinary page content: consider a visible usage notice and modest interaction friction. Keep the page usable and assume screenshots remain possible.
- To prevent your page from starting browser screen sharing: use
Permissions-Policy: display-capture=(), then verify the header and test the API behavior. Do not present it as blocking user screenshots. - For organization-owned devices: have IT evaluate Chrome Enterprise Premium or Edge’s managed policy against the organization’s license, platform mix, URL exceptions, and permitted capture paths.
- For paid video: use a compatible protected playback stack with authentication and watermarking, and test platform-specific behavior before making customer-facing promises.
If your requirement is “no visitor can ever make a copy,” none of these options meets it. Reconsider whether the content should be displayed to that visitor at all, or reduce the harm of a leak through access controls, lower-risk content, and traceable delivery.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. It does not disable screenshots; use it when you need to capture your own page to inspect what visitors actually see, for example after changing a banner, layout, or access flow. One GET request returns a PNG, JPEG, WebP, or PDF. Example request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners are accepted and removed, along with supported newsletter popups and chat widgets, before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response includes X-Page-Verdict and X-Billed headers. An MCP server lets AI agents use screenshot, page-info, and PDF-capture tools. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
Troubleshooting common problems
The Print Screen handler does nothing
The browser may not deliver the key event to the page, or the capture may be handled by the operating system or another application. Treat the handler as optional friction only; it cannot cover those paths.
Users can still start screen sharing
Confirm the response actually includes Permissions-Policy: display-capture=() and that the page or embedded document making the call is governed by that policy. The directive is about the page-initiated getDisplayMedia() API; it does not block system-level screen capture.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA browser ignores the policy or behaves differently
MDN identifies limited, experimental availability for display-capture. Test the browsers and versions your users have, and do not depend on uniform support. If a required API call fails with NotAllowedError, check whether your policy intentionally denies it before changing the header.
Managed users can still capture a page
Check that the device and browser are enrolled, the relevant policy is configured and applied, and the user is in scope. Then account for documented exceptions and alternative capture paths: Microsoft specifically warns that Edge Web Capture and methods outside the browser may remain available.
A DRM-protected stream can still be filmed or captured on one platform
Review the exact operating system, browser, hardware, and playback path involved. Protection varies by platform combination, and a camera is outside the playback software’s control. Use watermarking and access controls to reduce and investigate leaks rather than promising perfect prevention.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
