Help me understand the underlying iPAD file system

I have a 16GB iPAD2 (NOT jailbroken)


I am paranoid about orphaned files eating up disk space. Here is what bothers me ...


Let us take a typical scenario.


Via Safari I go to a site to get a PDF - I download the PDF and say "Open In" ... and choose "GoodReader".


Within the Goodreader filesystem I see this new file. I can view the PDF just fine but lets suppose that I want to now edit this file using yet another program (say, a program that has more PDF editing features). Via GoodReader I say "Open in" ... and the file opens in this other program. Lets call this program PDFEditor.


Now we have three programs that have three copies of this same file. I say this because if I delete the file within PDFEditor. It does not delete the file within GoodReader. As to Safari ... I have no idea where it caches the file. I suspect it has a copy of the file as well.


Can someone please explain to me how this all works. Again, I just want to avoid orphaned files taking up space.


Thank you //

iPad 2 Wi-Fi, iOS 5.0.1

Posted on Feb 2, 2012 6:32 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 2, 2012 8:38 AM

The underlying filesystem on the iPad is the standard OS X filesystem. In the iPad model, each application is a separate user and has it's own directory. In that directory, all of the application files are read-only, save for a single folder for user data. If you upgrade an application, the application data in the app directory is replaced, but the user data preserved. An application can only access files in it's home directory, and nowhere else.


Applications cannot access each other's directories at all. If you do an "Open In..." in an application, it's calling on an iOS service that copies the file from one application's data directory to the other's. There's no notion of sharing files (though, the core databases of Photos and Contacts can be accessed through a service and an application can refer to a photo or contact by a unique ID), except by copying them. It's up to the application whether or not it stores the file it receives temporarily or for an extended period of time. The implication of this model is also that deleting an app also deletes all the app's data and settings.


The fundamental difference between the desktop approach and the iPhone/iPad approach is that on the Desktop, information is associated with a user, whereas in iOS it's associated with and application. The iOS approach makes it impossible for applications to interfere with each other at the filesystem level, and it is one piece of the iOS security model.

8 replies
Question marked as Top-ranking reply

Feb 2, 2012 8:38 AM in response to vulcan_on_earth

The underlying filesystem on the iPad is the standard OS X filesystem. In the iPad model, each application is a separate user and has it's own directory. In that directory, all of the application files are read-only, save for a single folder for user data. If you upgrade an application, the application data in the app directory is replaced, but the user data preserved. An application can only access files in it's home directory, and nowhere else.


Applications cannot access each other's directories at all. If you do an "Open In..." in an application, it's calling on an iOS service that copies the file from one application's data directory to the other's. There's no notion of sharing files (though, the core databases of Photos and Contacts can be accessed through a service and an application can refer to a photo or contact by a unique ID), except by copying them. It's up to the application whether or not it stores the file it receives temporarily or for an extended period of time. The implication of this model is also that deleting an app also deletes all the app's data and settings.


The fundamental difference between the desktop approach and the iPhone/iPad approach is that on the Desktop, information is associated with a user, whereas in iOS it's associated with and application. The iOS approach makes it impossible for applications to interfere with each other at the filesystem level, and it is one piece of the iOS security model.

Feb 2, 2012 6:44 AM in response to vulcan_on_earth

I cannot explain the file system well. To me, it remains one of the fundamental differences between the windows approach and anything apple makes.


But there are a couple of tools. If you are looking for space hogs, go to settings, usage. When you give it a minute, it will list all of you apps and their size. If you tap an app, it will then show you the documents and media associated with that app. ( the size, not the individual components). So if your docs to go library starts to get out of hand, you will be able to see it.


For a full peek at the file system, find and download a program call iexplorer onto you computer. When you plug the pad in, a windows explorer type window pops up that shows all. But dont horse with it unless you are real clear about what you are doing. There are versions of this available for both mac and windows.

Feb 2, 2012 6:59 AM in response to pjl123

I noticed the limitation yesterday ... I found a free app in the AppStore that allows you to delete pages from wthin a PDF. So I thought fantastic. I have several magazines in PDF format. All of these are in GoodReader. The problem is that the edited PDF is a seperate file ... and I have to transfer it back to GoodReader and delete the old file. What a pain !!!!!

Feb 2, 2012 8:15 AM in response to vulcan_on_earth

I don't quite understand your issue, as what you're describing happens pretty much exactly the same way in the 'normal' world also.


  1. I download a file using Safari, or whatever, and it now resides on my Desktop.
  2. I open that file in Pages, edit and/or just save it ... it's now in Documents as a Pages file
  3. I open the original file in NeoOFfice, edit abd/or just save it ... another file in Documents as a .doc file
  4. and etc.


The iPad and iOS actually has no file handling system at all, no equivalent to Finder or Explorer. Everything is handled within apps, as you've noticed. You do point out that deleting a file in one app won't delete it in another app; I have no idea why you would want that to happen in most cases, and can think of all sorts of reasons why the OS would block off App A from playing around with the contents of App B.


Your final point is just semantics, a distinction which you no longer need now that you've understood it and one which, well, few if any others have ever had any issues with. If you're concerned enough about it you should contact Apple directly via their Feedback links and make your best case to them.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Help me understand the underlying iPAD file system

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.