Fast answer: YES Long answer: SQLite is advising against the use of Network file systems for multiple access to a single DB file, mostly because Network file systems *typically* do not handle file-locking correctly - that is to say, they lie about the file being locked when it isn't. (Ok, it's more involved than that, but not in the scope of this discussion). This means that as soon as any of those givens change, it's very safe to use. So as soon as: - 1. You do not have a Networking file system (but a local one), or - 2. You do not have multiple processes accessing the file, or - 3. Your Networked file system does not lie about locking. Then it's perfectly *safe* to use SQLite on. But... The other important consideration is that the bulk of the communication happens between the DB engine and DB files. A small percentage of typical data transfer happens to the end-client who asked for the data via a Query. This means that you typically would want the Engine *and* file to be on ONE device. For many use cases this is not a real factor, but for any DB with significantly big tables, this will matter. So yes, it can and will work if your file system guarantees locking semantics, but might still not be the optimal solution.