Hi,
I’ve just started using Firebase with my app, and I am wondering if there are any limits to it : I just want to particularly know about # of project buckets & items…
I searched up on the internet, but I could not find relevant docs of any limits of realtime database…
Please help me If you know anything 
you can see the limits/pricing here:
Thanks, @sketch & @catsarisky!
I found this snap :
What do they mean by GB stored & GB downloaded? I get the stored but what’s downloaded?
Stored is the size of your actual database. Downloaded would be downloads of data into your app. Or at least, that’s my best guess. 
If you go into Usage and Billing on your firebase’s project page, you can see something like this:
I’m not too worried about that project getting over the limit any time soon. 
download is how much the firebase server total download a day.
Firebase has very generous limits in the free package and the only issue is the number of times your app is getting data in a month which is the download limit.
Fill it up and query millions of records in under 1 second. I don’t think there’s a limit to bucket depth.
Pricing s on point if you get the blaze plan
I am still confused about the download limit - does downloading data into app mean the data I retrieve from DB? Do the item keys count in storing size?
Also, If I continue over the free plan & I am about to reach my limits, I can upgrade for pay as I go mode? Like $1/GB, etc.
Thanks!
The downloaded limit is all data transmitted from your FB to your app. Google will notify you when you are about to reach your limit.
1 byte = 1 character
Thanks, @muneer !
I get it now, Storage = size of my DB, and Downloads = the amount I retrieved. Thanks!
Also, do you know whether the keys of the items are considered or not in the bytes? Like the key customer has 8 characters, thus 8 bytes. And its value is let’s say kartik, which is 6 char. = 6 bytes.
So, if I retrieve the item customer, will it be considered as 8bytes + 6bytes = 14bytes OR just the size of the value, which is 6bytes?
Thanks!
Yes, keys are included and all the other stuff around them such as “:” that separate the key from the value and “,” that separate one key-value pair for the other.
But these are all bytes and you would not need to worry about them. The limit given is already generous.
Thanks a lot for your help! Well I am working on a big app, so I am trying to reduce the storage and retrievals as much as I can, so my DB doesn’t slow down 
Thanks a lot! 
Have a great day 
A good strategy is to retrieve a big chunk of data at once and save that as an app variable and then manipulate that data in the app instead of querying the database every now and then.
Of course this is useful for static or slow changing data. It will not be proper for dynamic ones.
Yes, That’s exactly what I am building. I have almost completed my code model around this idea
Thankfully, I do not have any dynamic/fast-changing data - so this works just perfect for me
Thanks!
