You cannot reliably prevent visitors from screenshotting content that a website has already displayed on their devices. A normal website does not control a visitor’s operating-system screenshot function. You can disable a page’s ability to initiate the browser’s screen-sharing API, and administrators can apply screenshot policies to some managed browsers and devices. Those measures have limited scope; they are not a guarantee that displayed content cannot be captured.
Can a website completely prevent screenshots?
No. A website can control some browser features and access to its own content, but it cannot reliably control every way a person can capture what is visible on their device. A visitor may have operating-system tools, browser features, extensions, another device, or other capture methods that the website cannot govern.
It helps to separate three different things that are often all called “screenshots”:
- A screenshot of the page: a user or their device captures pixels already shown in the browser. Ordinary site code has no universal switch for disabling this.
- Screen sharing initiated by a page: a site requests access through the browser’s Screen Capture API. The browser asks the user to choose what to share.
- Administrator-managed controls: an organization configures supported browsers on managed devices to restrict some capture or sharing routes.
The difference matters: restricting a web API or a managed browser policy does not make all the information rendered on a screen uncapturable.
Windows 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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
What a website can do: disable page-initiated screen capture
A site can use the display-capture Permissions-Policy directive to prevent its document from initiating the Screen Capture API through getDisplayMedia(). A typical HTTP response header is:
Permissions-Policy: display-capture=()
Configure the header on the server, CDN, or hosting platform so it is included in responses for the pages where you want this restriction. The exact configuration screen or syntax for setting a response header depends on your host. After deploying it, inspect the page’s response headers in your browser’s developer tools and verify that the policy is present.
When the policy disallows the feature, a call to getDisplayMedia() for that document can fail with NotAllowedError. This blocks that page’s ability to start this particular capture flow; it does not block a visitor from using their device’s screenshot controls to capture the page. MDN describes getDisplayMedia() as prompting the user to select a screen or part of one and returning a MediaStream. The user’s choice is part of the API’s design, not a site-controlled screenshot toggle. MDN currently labels the feature limited availability and not Baseline, so support is not universal.
Use this policy when your goal is to stop your own page from requesting display capture. Do not present it as a way to prevent screenshots of your site.
Recommended Free Tools
What managed browser policies can control
Organizations may have more options when they control the devices and browser configuration employees use. Whether a policy applies depends on the operating system, browser, management setup, licensing, and the capture method. Check current vendor documentation against the actual device fleet before relying on a policy.
| Control | Requirements and supported platforms in the cited documentation | Scope and limits |
|---|---|---|
Microsoft Edge DisableScreenshots policy |
Administrator control for supported managed environments. Microsoft lists Windows and macOS Edge 77 or later and Android Edge 146 or later; iOS is unsupported. The Edge policy documentation was last updated September 11, 2026. | Blocks screenshots taken through keyboard shortcuts and extension APIs. Microsoft warns that Web Capture within Edge and other methods outside the browser may still work. |
| Chrome screenshot-prevention policy | For managed users and browsers with a Chrome Enterprise Premium license. Screenshot prevention is available on Windows and Mac; screen-share prevention is supported on Windows. Linux is not supported for this setting. | Policy coverage is limited to its documented managed-browser and platform scope. Do not assume it disables every possible capture method or works on unsupported systems. |
These controls serve different purposes and have different prerequisites. Edge’s documented policy covers specified browser screenshot routes on supported platforms. Chrome’s documentation distinguishes screenshot prevention from screen-share prevention and attaches those controls to managed environments and a Premium license. Neither should be treated as a universal public-website setting.
Choose a policy by checking the deployment, not just the browser name
- Are endpoints managed? These are administrator controls, not settings an ordinary public website can impose on every visitor.
- Which operating systems and browser versions are in use? Match the fleet to the vendor’s supported platforms and versions. Edge’s listed minimums and unsupported iOS platform are material.
- What needs restricting? Decide whether the concern is browser screenshots, page-initiated screen sharing, or both. The controls are not interchangeable.
- Does the organization meet licensing and management requirements? Chrome’s documented screenshot prevention requires Chrome Enterprise Premium for managed users and browsers.
- Which exceptions and residual routes matter? Check whether particular sites need exceptions and whether browser features such as Edge Web Capture or methods outside the browser remain available.
Test the policy with the organization’s actual browser builds, operating systems, and approved capture workflows. A vendor’s documented scope is a better basis for deployment than an assumption that a policy blocks every route.
Why JavaScript tricks do not secure a page against screenshots
Scripts that intercept the Print Screen key, suppress right-click or context menus, block text selection, or place an overlay over an image may change a casual interaction. They do not take control of the visitor’s operating system or prevent all ways of recording visible pixels. A keyboard event handler cannot reliably veto a screenshot taken outside the page’s event system; disabling a context menu does not remove the displayed content from the screen.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →These approaches can also interfere with legitimate use, including keyboard navigation, assistive technology, copying text, and browser features. If used for a narrow interface reason, describe them accurately as interface restrictions—not screenshot security. The documented limits of managed browser controls make the broader point: even those controls can leave capture routes available.
Rank #4
Reduce exposure, discourage misuse, and improve traceability
For a public website, focus on the outcome you need rather than promising that capture is impossible. The following measures address different risks:
| Measure | What it helps with | What it does not do |
|---|---|---|
| Per-user or per-session visible watermark | Can deter casual redistribution and help attribute a leaked image when the mark identifies the viewer or session appropriately. | Does not stop capture. A watermark may be cropped or obscured, and it is not proof by itself of who made or distributed a capture. |
| Authentication and authorization | Limits which people can view protected pages or files. Use access checks on the server and grant only the access each user needs. | Cannot prevent an authorized viewer from recording content they can see. |
| Least-privilege delivery | Reduces how much sensitive material is exposed to each account or session, and for how long, where the application can enforce that. | Does not make information already displayed unrecordable. |
| Monitoring and audit records | Can help investigate suspicious access or distribution if the application has appropriate logs and a lawful, disclosed monitoring basis. | Does not stop an offline screenshot, and logs may not identify the person who actually captured or shared an image. |
| Clear use terms and organizational policy | Sets expectations and provides a basis for addressing misuse under applicable rules or agreements. | Is not a technical capture control. |
Apply privacy and data-protection requirements to any user-specific watermarking or monitoring. In particular, avoid collecting or exposing more personal information than the protection goal requires.
For protected premium video, investigate a suitable DRM delivery stack separately and evaluate its support for the exact browsers, devices, and distribution model you need. The sources discussed here do not establish a DRM implementation or a guarantee against screenshots, so do not treat DRM as an ordinary website-wide screenshot switch.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Comes with secure packaging
- It can be a gift item
- Easy to read text
A practical decision path
- If the site is public to any visitor: assume visible content can be captured. Use authentication for restricted material, limit exposure, and consider watermarks or monitoring for deterrence and attribution.
- If the goal is only to prevent your page from starting screen sharing: set
Permissions-Policy: display-capture=()on the relevant responses, then test the API behavior in browsers you support. Do not confuse that result with blocking screenshots. - If the devices belong to a managed workforce: compare Edge and Chrome policy requirements with your operating systems, browser versions, licensing, and required capture routes. Pilot the setting and test exceptions before broad deployment.
- If the content is high-value video: assess a DRM-based delivery approach as a separate platform and content-protection decision, with explicit testing for your target devices.
Or skip the browser setup
If your real need is to capture a clean image of a page for testing or automation—not to prevent visitors from taking screenshots—ScreenshotNeo is a screenshot API and MCP server for developers. It does not prevent screenshots on your site. For example, this cURL request captures a page to a WebP file:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Quick Recap
See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. Sign up for free ScreenshotNeo access.
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.
