FileOps MonitorRun your first scan
Review exclusions, then save the starting state of eligible files. This reference records what exists now.
WordPress file-change monitoring
Know which files changed.
A clearer starting point after a WordPress update or code edit. Run a manual scan and review added, modified and deleted files.
Local processing · No account required · Free on WordPress.org
Example report
Changes worth reviewingwp-config.phpModifiedwp-includes/version.phpModifiedthemes/…/functions.phpModifiedIllustration of a controlled test. A changed file is a reason to review—not proof of malware.
Three steps
Start with a reference. Compare after a change.
Run another scan
After an update or saved edit, start a manual scan. Refreshing the dashboard alone does not check files again.
See the differences
Review paths, change types and priorities. Accept a new reference only after checking legitimate changes.
Setup and a safe first test
Start on a staging or local site. Create an inert PHP file containing only a comment, such as wp-content/fileops-demo.php. Run your first scan, change only that comment, save, and run another scan. Confirm the modified path appears. Restore the exact original contents and scan again. Do not edit production core or credentials just to test the plugin. Removing the demo file later may correctly appear as a deletion.
Install and activate FileOps Monitor, then review Exclusions and run your first scan. A starting reference records the current files; it cannot reconstruct earlier edits.
Actual test evidence
Configuration, core and theme changes in one report.
A controlled local test detected edits in all three locations. The test files were restored afterward.
Choose your workflow
Manual checks today. Automation planned next.
FileOps Monitor Free
₹0
- Manual scans and SHA-256 comparison
- Added, modified and deleted file reports
- Exclusions and saved-reference management
- Local processing without source-content storage
Planned · Not yet available
FileOps Monitor Pro
₹1,000 / year, proposed
- Daily or weekly scheduled scans
- Grouped email alerts and weekly summaries
- Longer searchable history and CSV exports
- Scan-health reporting
Proposed for one production website. Features, tax treatment and terms will be finalized before sales open. No payment or registration is collected here.
A few useful distinctions.
Will it tell me whether a file contains malware?
No. FileOps Monitor reports differences from a saved reference. Review priority helps you decide what to investigate; it is not a malware verdict or repair function.
Why did an edit not appear?
Your reference may already contain the edit, the file may be excluded or unsupported, or you may be viewing an older completed scan. Save the file and run a new scan.
What does accepting current files do?
It creates a new comparison reference after you review legitimate changes. It does not repair, restore or edit your site files, and is not needed for routine scans.
Does Free run automatically?
No. Free scans are manual. Scheduled scans and email alerts are planned for the separate Pro add-on.
Does it monitor every file?
No. It monitors eligible code/configuration types within the WordPress root. Exclusions, unsupported binary/media files, symlinks and the 16 MB per-file limit affect coverage. Read the plugin documentation before relying on a report.
Where does my source code go?
Free processes files locally, stores hashes and metadata rather than source contents, and makes no external requests.
Try it on a test site.
Start with a saved reference and one harmless edit. See whether the report fits your maintenance workflow.