diff --git a/docs/concepts/faq.md b/docs/concepts/faq.md
index 79c62ae50..5c0b1ec10 100644
--- a/docs/concepts/faq.md
+++ b/docs/concepts/faq.md
@@ -63,6 +63,10 @@ If you want to develop an IPFS implementation or are already working on one, the
 
 In addition to these core documents, `specs.ipfs.tech` documents standards for IPFS subsystems such as the [InterPlanetary Naming System](https://specs.ipfs.tech/http-gateways/) and [HTTP Gateways](https://specs.ipfs.tech/http-gateways/).
 
+### Can I use IPFS offline?
+
+Yes, all locally pinned CIDs on an IPFS node are available offline. While the initial retrieval of content may require an internet connection, once the data is cached locally, it can be accessed offline. This is particularly useful in scenarios with intermittent connectivity or when creating applications for areas with limited internet access. 
+
 ## IPFS and Filecoin
 
 ### What is the connection between IPFS and Filecoin?
@@ -73,6 +77,7 @@ In short: IPFS addresses and moves content, while Filecoin is an incentive layer
 
 These components are separable - you can use one without the other, and IPFS already supports more self-organized or altruistic forms of data persistence via tools like [IPFS Cluster](https://ipfscluster.io/). Compatibility between IPFS and Filecoin is intended to be as seamless as possible, but we expect it to evolve. You can view the [draft spec for IPFS-Filecoin Interoperability](https://github.com/filecoin-project/specs/issues/143) and [ideas for future improvements](https://github.com/filecoin-project/specs/issues/144) to learn more.
 
+
 ## IPFS and Protocol Labs
 
 ### How are the IPFS Project and Protocol Labs related?