Name the product first
“Gemini resets at midnight” is incomplete advice. First establish whether you mean Gemini Apps with a personal Google account or a project using the Gemini API. Write that product name beside any limit you record. A useful reminder needs more context than the provider’s logo.
Google’s current personal-account Gemini Apps guidance describes compute-based limits that refresh over five-hour windows until a weekly limit is reached. Models and features can have additional limits. That is not a universal daily reset rule for everything called Gemini.
For Gemini Apps, use the account’s display
Open Gemini with the intended personal account and look under Settings → Usage limits. Identify the model or feature you were using when the restriction appeared. Read the specific limit and its timing, then copy the date and time if the screen provides them.
Keep a work or school account separate from this checklist: the cited consumer help page does not establish every organization’s rules. If the screen does not provide enough information, follow the help offered there rather than assigning a generic countdown. Unknown timing is more useful than a confidently wrong reminder.
For the API, check the project and limit dimension
Google documents Gemini API requests-per-day limits as project-level limits that reset at midnight Pacific time. This rule belongs to the API’s daily request allowance, not to the consumer app. Keep the Pacific time zone attached to it because its UTC offset changes with daylight saving time.
When investigating an API restriction, record the project, model, and exact limit mentioned in the response. A daily reminder will not explain a restriction measured over a different interval. Keep operational details in your own project notes and never paste API keys into a timer or public comment.
Create a reminder that says what it means
Use a label such as “Gemini Apps — personal — session” or “Gemini API — project nickname — daily requests.” These are examples of helpful names, not assumptions about what your account must show. Check the saved time once against the source you used.
For a concrete example, two reminders at the same clock time may still represent different products and different allowances. Treat them as separate records. When one completes, return to the corresponding app or project dashboard before assuming you can resume the other workflow.
- Match the reminder to the product, account or project, and limit type.
- Keep the time zone visible when converting a published schedule.
- If the official information changes, update your saved record.
- Do not treat a public service-status page as a view of your private quota.