Change a Logged Meal’s Time in Atomic Fast
Fix a saved meal’s date and time on iPhone or Android. Find the entry after moving it to another day, check the result, and understand what the edit leaves unchanged.
You remembered dinner the next morning and saved it under today’s date. Or the food is right, but the recorded time is an hour late. You can correct that meal without scanning it again or making another copy.
The short version
Open the saved meal in Meals, open its menu and choose Edit Meal Time. On iPhone, change the date and time, then tap Save. On Android, choose the date, tap Next, choose the time and tap Done. If you change the date, look for the meal on that date afterward; this edit keeps its foods and amounts and does not correct a fasting session.
Start with the existing entry
These instructions are for a meal that has already been saved. If you are still reviewing a new meal, set its Meal Time before saving instead. The guide to logging your first meal covers that earlier step.
Open Meals and select the date where the entry currently appears, even if that date is wrong. Tap the meal itself to open its details. Compare the name, foods and timestamp with the entry you meant to change. Similar breakfasts on consecutive days are easy to mix up.
Time editing is part of the free meal controls on both platforms. It does not request another AI analysis or use an AI scan. You do not need to grant a new camera permission to correct a saved timestamp. The labels below are the English labels; the app may display their translations in your selected language.
On iPhone: change both fields, then save
- Open the meal’s menu. In its details, tap the three-dot menu at the top. Choose Edit Meal Time.
- Check the date. The editor begins with the meal’s saved date and time. Open the date control and choose the day you actually ate. Leave it alone if only the time is wrong.
- Set the time. Adjust the hour and minute. Check the morning/evening designation if your phone shows a 12-hour clock. A date correction alone will not fix an incorrect hour.
- Tap Save. After the editor closes, read the timestamp under the meal’s name. Go back to Meals and select the corrected day if you moved it.
Cancel closes the editor without applying the selection. If saving reports an error, reopen the record and check its timestamp before trying again. A changed picker value by itself is not evidence that the record saved.
On Android: date first, then time
- Open the meal’s menu and choose Edit Meal Time.
- Choose the date in Select Meal Date. Keep the current date selected when only the time needs correction.
- Tap Next. This moves to Select Meal Time; it has not saved the change yet.
- Choose the hour and minute. Check AM or PM if those controls are shown, then tap Done.
- Check the result. A successful update shows Meal time updated. Read the saved timestamp, return to Meals and select its new day if necessary.
The Android date picker offers the year of the saved meal, the year before it and the year after it. For example, a meal dated in 2026 opens a picker covering 2025–2027. It is not an unrestricted history calendar. If you cannot select the intended year, cancel and keep the record intact while you seek help; do not enter a knowingly wrong date to fit the picker.
From the saved meal's menu
Two routes to the same correction
iPhone
- Edit Meal Time
- Choose date and time
- Save
One editor for both fields.
Android
- Edit Meal Time
- Select Meal Date
- Next → Select Meal Time
- Done
Next changes the step. Done submits the selection.
Then check the saved timestamp. A selected value is not a saved result.
A date correction moves the record’s place in history
Suppose you ate dinner on November 9 at 7:30 p.m., but recorded it on November 10 at 9:00 a.m. Open the meal from November 10, select November 9 and set 7:30 p.m. After saving, return to November 9 to find it. This is an illustrative correction, not a recommended mealtime.
The edit changes the existing meal’s timestamp. It does not create a second dinner or change its food items, quantities, calories or macros. Within a day, meals are listed by their saved times, with later entries first. Changing the time can therefore move a meal up or down the list even when its date stays the same.
Daily nutrition totals use the records assigned to that day. Moving a meal to another date changes which day’s total includes those recorded calories and macros. It does not recalculate the nutrition of the food itself. If the portion was also wrong, handle that separately through Edit Meal Items.
Illustrative record correction
Same dinner. A different date.
Before correction
November 10
9:00 a.m.
The date and time of logging were saved.
After correction
November 9
7:30 p.m.
The record now shows when dinner happened.
One existing meal
Same foods, portions and nutrition. Find it on the corrected day.
Check the timestamp, not every estimate
On iPhone, a time edit also updates the stored digestion-complete estimate and its summary when the meal already has an impact estimate. That is a calculation from the recorded meal, not a measurement of digestion.
Android’s time-edit action saves the timestamp but does not regenerate the stored metabolic-impact estimate. An older digestion-related time or summary can remain after a successful edit. Reopening the meal lets you verify its saved timestamp; it does not guarantee that the stored estimate has been recalculated.
The meal time and your fast’s start or end are separate records. This action does not start, end or move an existing fast. If both records are wrong, correct the fasting session’s times separately and check each result. Do not assume a meal edit repairs the timer because the entries now appear next to each other.
For an entry dated today, Today’s Timeline can help you read it alongside other activity. Use the Meals record when checking the exact saved timestamp or looking for an earlier date.
If the result looks wrong
The meal disappeared from the day you were viewing. Select the date you just saved. Check there before logging it again. Creating a replacement immediately can leave you with two records of the same meal.
The date is right but the time is wrong. Open Edit Meal Time again and inspect the hour, minute and AM/PM setting. Keep the correct date selected while fixing the time.
Android shows the meal near the boundary of two days. Its current day-list query includes the next midnight, so a meal saved at exactly midnight can appear in adjacent day lists. Around daylight-saving changes, the fixed-length day query can also misplace a boundary entry in the list. Open the details and inspect the timestamp before treating the appearance as a duplicate. Do not shift an accurate meal time just to change the list.
The edit did not persist. Leave the editor, reopen the meal and read the timestamp. If it still shows the old value, repeat the edit once and check again. If the problem continues, retain the entry and contact support with the steps and any error shown. Avoid deleting the meal as a first troubleshooting step.
Frequently asked questions
Can I correct a meal that I entered yesterday? Yes. Select the day where it is currently listed, open the meal and edit its time. On Android, the picker covers the saved meal’s year and the adjacent years.
Do I need to scan the food again? No. Time editing uses the saved meal. Use a food or portion edit only if those details also need correction.
Does Next on Android save the new date? No. Next opens the time step. Finish the date-and-time selection with Done, then verify the saved record.
Can I undo a time correction? There is no separate undo control in this flow. Before saving, use Cancel. After saving, reopen Edit Meal Time and enter the correct date and time again.
Sources and product notes
Product information checked: November 10, 2026.
Product verification: We traced the Meals entry points, localized editing labels, date/time pickers, save handlers and selected-day queries in the current iPhone and Android source, together with meal-logging and free-tier documentation. The Android year range, day-boundary behavior and unchanged impact estimate were checked separately. This was code and documentation review, not a device walkthrough. Detailed paths and revisions are retained in the editorial review record. No clinical study is needed to establish these editing controls, and changing a record does not verify its nutritional or physiological estimates.
Get Atomic Fast on the App Store or Google Play.