I have a folder where I transfer home videos from a camcorder to. I find two files in this folder that are not videos...

  1. .fuse_hidden0000002c00000001
  2. .fuse_hidden0000002600000002

What are these files, and can they be safely deleted?

  • 1
    Refer Wikipedia – user308564 Jul 8 '14 at 16:13
  • 2
    @user308564: And, how does that help? – skrtbhtngr Nov 21 '16 at 22:02

You can safely ignore .fuse_hiddenXXXX files. It means a file was deleted but there is at least one software which is still using it, so it can't be removed permanently.

It will be done automatically when the relevant software stops using the file or exists. Such files are always gone after umount/reboot. This is how Linux and any Unix works but only FUSE exposes these files to the user.

These are likely files that were meant to be deleted but are somehow still in use.UBF

  • 3
    What created these files? – barrypicker Jul 10 '14 at 4:26
  • 11
    You can find out what application has the file open by using the lsof command. lsof /full/path/name/to/file. These files are also related too the ntfs-3g file system. – Mitch Jul 10 '14 at 8:31
  • @Mitch: lsof /full/path/name/to/file doesn't show anything for my ` .fuse_hiddenXXXX` file. – Tim Dec 8 '14 at 13:57
  • 1
    Try lsof /just/the/directory/path instead, that lists everything that has a file open in that directory. Worked for me. – dr. Sybren Apr 9 '15 at 9:53
  • 2
    After a hard reboot, I found a bunch of these files but lsof revealed that no process was using them. I deleted them without a problem and nothing bad happened. – mhernandez Jan 22 '17 at 17:22

I had such a file, and I was unable to delete the folder it was located in.

Turns out it was a vim swap file. Closing the vim session(in another terminal) solved the issue.


I had 10GB of fuse files in my Downloads that had a last-modified date of a year and a half ago, so I just deleted them. I ran the lsof command above and it didn't show anything using the file (which would have been really surprising)

I'll uhhh... update this answer I guess if I notice anything went badly from that.


for me, it was Sonarr that was creating these keepalive files. I have Sonarr running in a docker, with access to the tv-shows on another server. On this server, the files are being created. Stopping the docker container allowed me to remove the files permanently.

  • Were the files not removed automatically when the docker container was stopped as explained in the accepted answer? – Elder Geek Jul 23 '19 at 13:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.