When you sync a SharePoint library to File Explorer, some files may appear with a read-only icon or cannot be edited. This happens even when you have Full Control or Edit permissions on the site. The root cause is often a combination of file checkout settings, library permissions, or synchronization conflicts that block write access. This article explains why synced files become read-only and shows site owners how to verify and fix the settings that control file editing in a synced library.
Key Takeaways: Fixing Read-Only Files in a Synced SharePoint Library
- Library settings > Require Check Out: Disabling this setting allows multiple users to edit files without locking them as read-only for others.
- SharePoint admin center > Sharing policies: Ensure external sharing and anonymous access policies do not force files to open as read-only.
- OneDrive sync client > Pause sync: Temporarily pausing and resuming sync can clear temporary read-only flags caused by sync conflicts.
Why Synced Files Become Read-Only in SharePoint
SharePoint libraries have several settings that can cause files to appear as read-only when synced to File Explorer. The most common cause is the Require Check Out setting. When this is enabled, a file is locked after it is opened by one user. Other users see the file as read-only until the first user checks it back in. This behavior is by design, but it often surprises site owners who expect everyone to edit simultaneously.
Another cause is permission inheritance. If a library or folder has unique permissions that remove the Edit or Contribute permission level for a user, that user sees files as read-only. Additionally, the OneDrive sync client may apply a temporary read-only flag when a sync conflict occurs, such as when a file is open on another device or being updated by a co-author.
Finally, file type restrictions in SharePoint can mark certain file extensions as read-only by default. For example, PDF files are often opened as read-only unless the library is configured to allow editing. Site owners should check all these areas before troubleshooting individual user issues.
Steps to Check Library Settings and Fix Read-Only Files
Follow these steps to identify and correct the settings that cause read-only files in a synced SharePoint library. Perform these steps as a site owner or site collection administrator.
- Open the library settings page
Navigate to your SharePoint site. Select the library that has read-only files. Click the gear icon in the top-right corner, then select Library settings. If you do not see this option, you may not have owner permissions. - Check the Require Check Out setting
In the Library settings page, under General settings, click Versioning settings. Look for the Require Check Out option. If it is set to Yes, files will be locked when someone opens them. Change it to No to allow multiple users to edit files simultaneously. Click OK to save. - Verify permission inheritance
In Library settings, click Permissions for this document library. If you see the message “This library inherits permissions from its parent,” permissions are inherited. If you see unique permissions, click Check Permissions and enter a user name to see their effective permission level. Ensure the user has at least Contribute or Edit access. If not, add the user to a group with those permissions. - Clear sync conflicts in OneDrive
On the affected computer, right-click the OneDrive icon in the system tray. Select Pause syncing for 2 hours. After the pause, right-click the icon again and select Resume syncing. This forces the sync client to re-evaluate file states and can remove temporary read-only flags. - Check file type editing permissions
In the library, select a file that appears read-only. Click the three dots (ellipsis) and select Details. In the details pane, look for Editing status. If it says “This file type cannot be edited in the browser,” the file may be a PDF or other read-only format. For PDFs, you can edit them in a desktop app if you have the appropriate software. No library setting changes this behavior.
If SharePoint Still Shows Read-Only Files After the Main Fix
Sometimes the main settings are correct, but read-only files persist. These additional issues and their fixes cover the most common remaining causes.
Read-Only Files Caused by Anonymous or Guest Access Links
If you shared a file or folder using an anonymous access link (Anyone with the link), those users see files as read-only by default. To allow editing via a link, you must change the link type. In the library, select the file, click the three dots, and choose Manage access. Under Link settings, change the link type from Anyone with the link to People in your organization or Specific people. Then set the permission level to Can edit. Anonymous links cannot grant edit permissions in most SharePoint configurations.
Files Stuck as Read-Only After a Co-Author Edits
When two users edit a file simultaneously, the second user may see a read-only copy after saving. This is not a permission issue but a merge conflict. The OneDrive sync client creates a copy of the file with a conflict label, such as “filename (User’s conflicted copy).” The original file remains read-only until the conflict is resolved. Open the conflicted copy, merge the changes manually, and delete the conflicted copy. The original file will then become editable again.
Library with Information Rights Management (IRM) Enabled
SharePoint libraries that use IRM to restrict file actions may force files to open as read-only even for users with Edit permissions. To check this, go to Library settings and click Information Rights Management. If IRM is enabled, review the policy settings. Look for the option Do not allow users to print or Do not allow users to copy content. These settings do not directly cause read-only, but the IRM policy may restrict editing for certain file types. Consider disabling IRM for the library if it is not required.
Library Settings vs User Permissions: Key Differences for File Editing
| Item | Library Setting | User Permission |
|---|---|---|
| Effect on file | Require Check Out locks file after first open | Read permission shows file as read-only |
| Who can change it | Site owner or library owner | Site owner or permission manager |
| How to verify | Library settings > Versioning settings | Library settings > Permissions > Check Permissions |
| Fix action | Disable Require Check Out | Add user to group with Edit or Contribute |
| User sees | Read-only while another user has file open | Read-only for all files in library |
Site owners can now identify why synced library files appear read-only and apply the correct fix. Start by checking the Require Check Out setting in the library versioning settings. Next, verify that users have at least Contribute permissions. If issues remain, check for sync conflicts or IRM policies. As an advanced tip, use the SharePoint PnP PowerShell module to bulk-disable Require Check Out across multiple libraries with the command Set-PnPList -Identity “LibraryName” -EnableVersioning $true -RequireCheckout $false.