When you move a file from one SharePoint document library to another, the file may open as read-only for some users. This happens because SharePoint retains the original permission inheritance or metadata from the source library. The file is not corrupt, but users cannot edit it until the read-only state is removed. This article explains why files become read-only after a move and provides the exact steps to prevent or fix this issue.
Key Takeaways: Preventing Read-Only Files After Moving
- Check-in required for co-authoring: Files that are checked out in the source library remain checked out after the move, causing a read-only state for others.
- Permission inheritance break: Moving a file to a library with unique permissions can break inheritance and lock the file for users without explicit edit rights.
- Use Move or Copy with version history: Using the SharePoint Move or Copy command preserves permissions and prevents read-only locks better than dragging files.
Why a File Opens Read-Only After Being Moved Between Libraries
When you move a file between SharePoint libraries, the file system does not always transfer the permission and metadata state cleanly. The most common cause is that the file was checked out to a user in the source library. SharePoint retains the checkout status even after the move. This means the file is considered locked by the original user, and everyone else sees it as read-only.
Another cause is permission inheritance. If the source library inherits permissions from the site but the destination library has unique permissions, the moved file inherits the destination library’s permissions. If a user does not have edit permissions on the destination library, the file opens as read-only for that user.
A third cause is metadata or content type mismatch. If the destination library requires a required metadata field that the moved file lacks, SharePoint may block editing until the field is filled. This is less common but can appear as a read-only state.
Steps to Prevent Files From Opening Read-Only After Moving
Follow these steps to ensure files remain editable after being moved between libraries. Perform these checks before and after the move.
- Check Out Status in the Source Library
Before moving any file, open the source library and verify that no file is checked out. In the library, click the file name and look at the status column. If the file shows “Checked Out to [username],” ask that user to check it in. You can also force a check-in if you have owner permissions. Go to the library settings and select “Manage checked out files” to check in all files. - Use the SharePoint Move Command Instead of Drag-and-Drop
Drag-and-drop in File Explorer or in the browser can break permission inheritance. Instead, select the file, click the ellipsis (three dots), and choose “Move to” or “Copy to.” This command preserves the file’s metadata, version history, and permission inheritance where possible. - Verify Destination Library Permissions
Before moving, check the destination library’s permission settings. Go to the library, click the gear icon, select “Library settings,” then “Permissions for this document library.” Ensure that all users who need to edit the file have at least Contribute permission. If the library uses unique permissions, grant edit access to the required users. - Match Required Metadata Fields
If the destination library has required columns, ensure the file has values for those columns before or immediately after the move. You can edit the file properties by clicking the file, selecting the ellipsis, and choosing “Properties.” Fill in any empty required fields. If a required field is missing, SharePoint may block editing. - After the Move, Check the File’s Read-Only State
After moving the file, open it in the browser. If it opens as read-only, close it. Go back to the library, select the file, and click the ellipsis. Choose “Details” and look for a lock icon. If the file is checked out, check it in. If the file shows a permission error, adjust permissions as described in step 3.
If the File Still Opens Read-Only After These Steps
If the file remains read-only, the issue may be a browser cache or a file lock from the previous location. Clear the browser cache and try opening the file again. If the file was moved using a third-party tool or script, the metadata may be corrupted. In that case, delete the file from the destination library and re-upload it using the SharePoint Move command.
If the File Still Opens Read-Only After the Main Fix
“File opens read-only in Word Online but not in the desktop app”
This usually indicates a co-authoring conflict. Word Online may show the file as read-only if another user has the file open in the desktop app. Ask all users to close the file. If the issue persists, go to the library, select the file, click the ellipsis, and choose “Manage access.” Remove any temporary access that may be locking the file.
“File shows a lock icon after moving to a different site collection”
Moving a file between site collections can break permission inheritance entirely. The file may inherit permissions from the root site instead of the destination library. To fix this, go to the destination library, select the file, and click “Manage access.” Add the correct users or groups with edit permissions. You may need to break permission inheritance for the file and assign unique permissions.
“Error message: This document is locked for editing by another user”
The file was checked out in the source library and the checkout status was not cleared during the move. As a site owner, you can force a check-in. Go to the library settings, select “Manage checked out files,” and check in all files. If the file is not listed, use SharePoint Designer to remove the lock, or contact Microsoft Support.
Move Methods and Their Effect on Read-Only Status
| Move Method | Preserves Permissions | Preserves Check-Out Status | Preserves Version History |
|---|---|---|---|
| SharePoint Move command | Yes, within same site collection | No, check-out is cleared | Yes |
| Drag-and-drop in browser | No, permissions may reset | Yes, check-out remains | No |
| File Explorer drag-and-drop | No, permissions reset | Yes, check-out remains | No |
| Copy to then delete source | No, permissions reset | No, check-out is cleared | No |
The SharePoint Move command is the safest method for moving files between libraries within the same site collection. For cross-site collection moves, use the Copy to command and then manually adjust permissions. Avoid drag-and-drop methods because they preserve the checked-out state and break permission inheritance.
You can now move files between SharePoint libraries without triggering a read-only state. Always check the checkout status before moving and use the SharePoint Move command. For files that already show read-only, force a check-in and verify permissions in the destination library. As an advanced tip, create a library view that shows the “Checked Out To” column and the “Permission Match” column to quickly identify problem files before moving them.