title: How does Firebase calculate cloud storage uses?
body: <p>My project deals with Business, their products and customers. Every business, product and customer (user) has its unique ID. In my cloud storage, I have around 30 images. Image size is around ~60/70KB. Even if I take 100KB each, the total is just 3MB.</p>
  <p>The project is still in development, I'm keeping these images for testing purpose. I'm not updating any new image but my byte storage keeps rising. I even deleted some images but it keeps increasing. I don't understand and I couldn't find the answer. Someone, please explain.</p>
  <p>As you can see here in the image, the byte stored is almost 5GB. When I manually calculate all the images, it's not even 3MB.</p>
  <p><a href="https://i.stack.imgur.com/P1H3z.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/P1H3z.png" alt="enter image description here" /></a>
  <a href="https://i.stack.imgur.com/0oGpZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0oGpZ.png" alt="enter image description here" /></a></p>
  <p><strong>Here is the hierarchy of my cloud storage.</strong></p>
  <ol>
  <li>Whenever a customer upload/update their profile picture, that image will be saved here in this <strong>&quot;UserProfile&quot;</strong> collection and the name of the image will be the user ID.</li>
  </ol>
  <pre><code>UserProfile (Collection)
      - user_1.jpeg
      - user_2.jpeg
      -
      -
      - user_n.jpeg
  </code></pre>
  <ol start="2">
  <li>Business can have many profile images. Those images will be store under <strong>&quot;BusinessProfile\{business_id}\...&quot;</strong></li>
  </ol>
  <pre><code>BusinessProfile (Collection)
      - Business_1 (Sub-Collection)
          - businessImage1.jpeg
          - businessImage2.jpeg
          -
          -
          - businessImageN.jpeg
      - Business_2
      -
      -
      - Business_n
  </code></pre>
  <ol start="3">
  <li>A product can also have many product images. Those will be store under <strong>&quot;ProductImage\{business_id_which_the_product_belongs}\{product_id}\...&quot;</strong></li>
  </ol>
  <pre><code>ProductImage (Collection)
      - Business_1  (Sub-Collection)
          - Product_1 (Sub-Collection)
              - productImage1.jpeg
              - productImage2.jpeg
              -
              -
              - productImagen.jpeg
          - Product_2
          -
          -
          - Product_N
      - Business_2
      -
      -
      - Business_3
  </code></pre>
  <p>Usually, in other people's design, they'll keep like 3 collections only to store the images and store the image URLs to the document of the user or business or product.
  The reason why I have this structure with sub-collections is that this way whenever I need the image in the App, I can generate the URL of the image from the ID without retrieving the document data (Just trying to optimize no. of Firebase doc reads).</p>