Fence view
A screen overlay of bars or a grid that blocks casual screen-scraping and photography while a document is on screen.
Fence view is a screen protection layer that a virtual data room paints over a document the moment it opens in the browser. Instead of showing a clean, fully legible page, the room renders a pattern of moving bars, a mesh grid, or a spotlight that keeps only a small area sharp while the rest stays dimmed or blurred. A logged-in reviewer can still read the file by moving their cursor or eyes across the page, but anyone glancing over their shoulder, filming the monitor, or trying to snap a phone photo captures a broken, striped image that is hard to reassemble. The point is not to stop the authorised reader; it is to defeat the analogue hole, the gap that watermarks and download blocks cannot close, where a screen is simply photographed by a second device.
How does fence view work in a data room?
Fence view is applied at the rendering layer, not to the stored file. When a permitted user opens a document, the data room streams it as protected on-screen output and composites an overlay on top: static or animated bars, a dotted grid, or a follow-the-mouse spotlight. Because the mask lives in the viewer rather than in the file, the original document is never altered and nothing legible sits in the browser cache. Administrators usually switch it on per folder, per file, or per user group, and pair it with view-only access so the same reviewer who cannot download a file also cannot lift a clean screenshot of it. On most platforms fence view is one toggle inside a broader rights profile governed by information rights management, which decides who opens what and under which restrictions.
It is worth being precise about what fence view does and does not do. It raises the effort and lowers the quality of a casual capture; it does not make a determined, patient copyist impossible. That is why it is deployed as one layer among several rather than as a standalone guarantee.
Why does fence view matter for M&A and due diligence?
In a sell-side M&A or fundraising process, dozens of outside parties, competing bidders, their lawyers, and their advisers, page through the same confidential documents. The sensitive risk is not always a bulk download; it is a single financial model or customer list photographed off a laptop in a coffee shop and forwarded. Fence view narrows that gap by making an off-screen capture visibly degraded.
The security payoff is strongest when fence view is combined with tracing. Dynamic watermarking stamps the viewer’s name, email, time, and IP across each page, so if a leaked image does surface, it points to a source; fence view makes that image harder to produce cleanly in the first place. Prevention plus attribution together are far stronger than either alone. For a fuller walk-through of how the two features complement each other, see our guide on dynamic watermarking and fence view, and for the wider control set our VDR security features checklist.
A concrete example
A private-equity firm opens a data room to four rival bidders during a competitive auction. The target’s three-year financial model is set to view-only, watermarked with each viewer’s identity, and wrapped in fence view. A junior analyst at one bidder tries to photograph the model on a phone to share with a colleague who lacks room access. The photo comes back as a bank of dark vertical bars with only a sliver of numbers visible, and every readable fragment carries the analyst’s own name and timestamp. The shortcut is useless, so the analyst has to work inside the room where every action is logged. That is fence view doing its job, not by blocking the eye, but by breaking the camera.
How should you evaluate fence view, and what goes wrong?
Treat fence view as a real but partial control, and test it before you rely on it. Common mistakes include assuming it stops screenshots on its own (it degrades them, it does not always forbid the OS-level capture), enabling it so aggressively that legitimate reviewers strain to read and start requesting downloads instead, and forgetting that it protects the screen but not a file already exported to PDF. Evaluate it hands-on rather than from a spec sheet.
| What to check | Good sign | Warning sign |
|---|---|---|
| Readability for the authorised viewer | Text stays comfortably legible as the eye or cursor moves | Reviewers complain and ask for downloads instead |
| Camera resistance | A phone photo of the screen comes out broken and hard to read | A still photo captures a clean, forwardable page |
| Scope of control | Set per file, folder, and user group | All-or-nothing, one global switch only |
| Pairing with other layers | Works alongside watermarking and view-only access | Sold as a standalone anti-leak fix |
| Cross-device behaviour | Holds up on external monitors and tablets | Overlay drops out on a second screen |
When you compare vendors, look at how these screen controls are packaged and priced rather than whether the box is merely ticked. Our side-by-side comparison shows which providers include fence view in their standard security tier and which gate it behind an upgrade, and individual provider reviews note how each implementation held up in hands-on testing. Pricing shown across the site is indicative; confirm the current figure with the provider.
FAQ
Does fence view stop screenshots completely? No. Fence view degrades a capture rather than forbidding it outright. A screenshot or phone photo still records something, but the striped or grid overlay makes the result fragmentary and hard to reassemble. Combined with dynamic watermarking, any fragment that does leak still carries the viewer’s identity, which is why the two controls are almost always used together.
Can an authorised reviewer still read the document normally? Yes. Fence view is tuned so the person actually working in the room can read the page by moving their cursor or gaze, keeping a small area sharp while the surrounding overlay stays dense. If reviewers find a document genuinely hard to read, the setting is usually too aggressive and should be dialled back.
Is fence view the same as view-only access? No, though they pair naturally. View-only access removes the ability to download, print, or edit a file, while fence view protects what is shown on the screen against cameras and shoulder-surfing. A well-configured data room typically applies both at once, under an information rights management profile, so a sensitive file can be neither exported nor cleanly photographed.
