How to Distinguish SharePoint Audit Events for Downloads and Views
Question details
The user needs to differentiate between a document being viewed in the browser and being downloaded to a local device within SharePoint Server 2019.

- Product
- SharePoint Server 2019
- Device & OS
- not provided
- Scenario
- Administrators attempting to accurately track user activity and secure sensitive documents on an on-premises SharePoint deployment.
- Observed behavior
- SharePoint Server 2019 standard audit logs group document opening, viewing, and downloading actions together under a single 'View' event, making it impossible to tell if a file was actually downloaded.
Ensure you have server administrator or farm administrator privileges, as resolving this requires accessing internal IIS server logs or deploying custom solutions.
Analyze IIS Logs to Identify Download Patterns
Since native SharePoint audit logs do not distinguish the actions, parsing IIS logs allows you to look at raw HTTP traffic to determine if a download occurred.
IIS (Internet Information Services) logs record every HTTP request made to your SharePoint server. By examining the byte transfer size and the specific endpoints hit, administrators can deduce which 'View' events were actual file downloads.
Navigate to the default IIS log directory on your SharePoint server, typically found at %SystemDrive%\inetpub\logs\LogFiles.
Filter the log files for HTTP GET requests targeting specific document file types, such as .docx, .xlsx, or .pdf.
Look at the 'sc-bytes' (bytes sent by the server) column. A full file download will typically show a byte count matching the file size, whereas a browser view might transfer fewer bytes or utilize specific Office Online Server endpoints.
Match the timestamp and the client IP address from the IIS log back to the standard SharePoint 'View' event to confirm the user identity.

Develop Custom Event Receivers
Create a custom coded solution to hook into SharePoint document libraries and log specific download actions.
Consult the Microsoft Q&A Community
Seek deployment-specific guidance or third-party auditing product recommendations from specialized SharePoint experts.
Handle Enterprise Documents Seamlessly with WPS Office
While resolving server-side auditing constraints requires administrative configuration, managing the actual documents shouldn't be a hassle. WPS Office offers a lightweight, highly compatible suite to effortlessly open, edit, and collaborate on documents downloaded from your enterprise SharePoint servers.
- 1. Download the software: Get the free WPS Office installation package from the official website and install it on your PC or Mac.
- 2. Open downloaded documents: Locate the .docx, .xlsx, or .pptx files you downloaded from SharePoint and open them directly in WPS Office without formatting loss.
- 3. Edit and save efficiently: Utilize the comprehensive editing tools to update your work, then save it locally or upload it back to your SharePoint document library.

Frequently Asked Questions
Why does SharePoint 2019 group downloads and views together?
In on-premises SharePoint Server 2019 environments, both opening a document in the web browser and downloading a copy trigger similar file read operations on the backend database. The native audit engine does not distinguish between the client applications requesting the read, logging both simply as a 'View' event.
Does SharePoint Online have this same auditing limitation?
No. SharePoint Online utilizes the Microsoft 365 unified audit log, which features more granular tracking capabilities. It can successfully differentiate between 'Accessed file' (viewing in a browser) and 'Downloaded file' events.
Can third-party auditing tools accurately separate views from downloads?
Yes. Many third-party enterprise auditing solutions designed for SharePoint Server bypass the native audit limitations by actively parsing IIS traffic, intercepting server-side events, and correlating multiple data points to deliver highly accurate reports on user downloads.




