DE

↑ ↓ select, Enter open, Esc close

Find files modified between two dates

harmlessFilesystemalle
Adjust the values, the command updates live
user@server
find /var/www/vhosts/example.com/httpdocs -type f -newermt '2026-10-01' ! -newermt '2026-10-08' -printf '%TY-%Tm-%Td %TH:%TM  %p\n' | sort

Finds files last modified after the start date and before the end date and prints them sorted with their timestamp. Both dates start at 00:00, so the end date itself is not included. Useful for narrowing down the timeline of an incident or tracing the changes of a deployment.

Note: Times work too, for example '2026-10-08 14:30'.

Also searched as

  • find files modified between two dates linux
  • what changed last week
  • filter files by modification date
  • find files changed on a specific day

Related one-liners

All in Filesystem

Find files modified in the last minutes

$find /var/www/vhosts/example.com/httpdocs -type f -mmin -60 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r
harmlessFilesystem

Find files older than X days

$find /var/www/vhosts/example.com -type f -mtime +30 -printf '%TY-%Tm-%Td %p\n' | sort | head -100
harmlessFilesystem

Show all timestamps and permissions of a file

$stat /var/www/vhosts/example.com/httpdocs/wp-config.php
harmlessFilesystem

Find recently modified PHP files

$find /var/www/vhosts/example.com/httpdocs -type f -name '*.php' -mtime -7 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r
harmlessSecurity

Calculate the total size of all files of one type

$find /var/www/vhosts/example.com/httpdocs/wp-content/uploads -type f -iname '*.mp4' -printf '%s\n' | awk '{s+=$1; n++} END {printf "%d Dateien, %.1f MB\n", n, s/1048576}'
harmlessFilesystem

Delete empty directories recursively

$find /var/www/vhosts/example.com/httpdocs -mindepth 1 -type d -empty -print -delete
destructiveFilesystem

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.