How to Check In a File in SharePoint
Checking in releases a file back to the team and creates a clean version with a description. It’s also where major vs minor versioning gets decided.
What it is
Checking in is the other half of check-out. When you’re done with your changes, you check the file back in — which makes your edits visible to everyone, releases the lock, and creates a new version in the file’s history. It also gives you the chance to add a comment describing what you changed, which becomes part of the audit trail.
Check-in is also where you make a decision: is this a minor version (a small update, still being refined) or a major version (a significant, formally released update)? Minor versions are often labelled 0.1, 0.2, 0.3 — drafts in progress. Major versions are 1.0, 2.0, 3.0 — published or approved versions. Not every library uses major/minor; smaller teams often just have major versions.
The check-in comment matters more than people think. Six months from now, someone (possibly you) will look at version history and try to understand what happened. ‘Updated’ tells them nothing. ‘Replaced section 4 with new policy following Legal review’ tells them everything they need to know.
When to use this
- When you’ve finished editing a checked-out file.
- When you need to make your changes visible to others.
- When you’ve reached a meaningful milestone in a long-running edit.
- Before going on leave, so the file isn’t locked while you’re away.
How to do it
- Open the SharePoint library where the checked-out file lives.
- Select the file (the green arrow shows it’s checked out to you).
- Click More options and select Check in.
- Choose major version (significant, released change) or minor version (small, still-in-progress update) if the library uses both.
- Add a clear check-in comment describing what changed.
- Confirm to release the file.
- Verify the latest version opens correctly for other users.
Best practices
- Always write a meaningful comment. Future you will be grateful. ‘Done’ is not a meaningful comment.
- Use major versions for released, approved content. Minor versions for drafts and in-progress work.
- Don’t check in partial work as a major version. Save it as minor (or keep it checked out) until it’s actually ready.
- Sanity-check after check-in. Open the file once after check-in to make sure formatting and content saved as expected.
Common mistakes
- Skipping the comment. Version history without comments is just a list of dates. Useless for audit.
- Checking in everything as a major version. Every tiny tweak becomes ‘v.4.0’, ‘v.5.0’, ‘v.6.0’. Major versions lose their meaning.
- Forgetting to check in at all. The file stays locked and your colleagues can’t edit. Check the library before you log off.
The SharePoint Essentials System is the most comprehensive end-user guide in the range. 7 modules, 35 slides covering navigation, libraries, views, lists, metadata, permissions, and decision trees — updated for the new 2026 SharePoint App Bar.
Get the Essentials System — $37 →FAQ
How do I check in a SharePoint file?
Right-click the checked-out file, choose More, then Check in. Add a comment describing the change (this appears in Version History). Choose major or minor version. Click Check In. The file is available for others to edit again.
What’s the difference between a major and minor SharePoint version?
Minor versions (e.g. 0.1, 0.2, 0.3) are drafts visible only to people with edit rights. Major versions (e.g. 1.0, 2.0, 3.0) are published versions visible to everyone with read access. Use minor versions during drafting, major when ready to publish.
Why is my SharePoint check-in failing?
Three common causes: another user holds the file open in desktop app (close it everywhere first); the file is locked by a workflow or sensitivity label; or someone else has checked it out under their account (only that person or a site owner can check in). Check the file’s check-out status in the library.
Can I discard a SharePoint check-out without saving changes?
Yes — right-click the checked-out file, choose More, then Discard check-out. All changes you’ve made since checking out are lost; the file reverts to its state at check-out. Useful if you started edits and decided not to proceed.