WaitForSeconds and WaitForEndOfFrame in Unity - Step-by-Step Execution

Concept Flow - WaitForSeconds and WaitForEndOfFrame

Start Coroutine

↓

Yield WaitForSeconds

↓

Wait real time seconds

↓

Resume after delay

↓

Yield WaitForEndOfFrame

↓

Wait until frame ends

↓

Resume next frame

↓

Coroutine ends

The coroutine pauses at WaitForSeconds for a set time, then resumes and pauses again at WaitForEndOfFrame until the current frame finishes, then continues.

Execution Sample

Unity

IEnumerator Example() {
  Debug.Log("Start");
  yield return new WaitForSeconds(2);
  Debug.Log("After 2 seconds");
  yield return new WaitForEndOfFrame();
  Debug.Log("End of frame");
}

This coroutine logs a message, waits 2 seconds, logs again, waits until the frame ends, then logs a final message.

Execution Table

Step	Action	Yield	Wait Time / Condition	Output
1	Start coroutine	None	None	Logs: Start
2	Yield WaitForSeconds	WaitForSeconds	2 seconds real time	Pauses coroutine
3	Resume after 2 seconds	None	Time passed	Logs: After 2 seconds
4	Yield WaitForEndOfFrame	WaitForEndOfFrame	Until current frame ends	Pauses coroutine
5	Resume after frame ends	None	Frame finished	Logs: End of frame
6	Coroutine ends	None	None	Coroutine stops

💡 Coroutine stops after completing all yield instructions

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
Coroutine State	Not started	Waiting 2 seconds	Waiting end of frame	Completed

Key Moments - 3 Insights

Why does the coroutine pause at WaitForSeconds?

Because WaitForSeconds tells Unity to pause the coroutine for the specified real time seconds before continuing, as shown in step 2 of the execution_table.

What does WaitForEndOfFrame wait for exactly?

It waits until the current frame finishes rendering before resuming the coroutine, as shown in step 4 and 5 of the execution_table.

Does WaitForSeconds wait for game frames or real time?

WaitForSeconds waits for real time seconds, not frames, so it can pause across multiple frames, as seen between steps 2 and 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the coroutine state after step 2?

A Waiting end of frame

B Waiting 2 seconds

C Completed

D Not started

💡 Hint

Check variable_tracker row 'Coroutine State' after step 2

At which step does the coroutine resume after waiting for the frame to end?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

See execution_table step 5 where it logs 'End of frame'

If WaitForSeconds was changed to 0, what would happen at step 2?

A Coroutine pauses for 2 seconds

B Coroutine pauses until frame ends

C Coroutine continues immediately without pause

D Coroutine stops

💡 Hint

WaitForSeconds with 0 means no delay, so coroutine continues immediately after step 2

Concept Snapshot

WaitForSeconds pauses coroutine for given seconds (real time).
WaitForEndOfFrame pauses coroutine until current frame finishes rendering.
Use yield return with these to delay actions.
WaitForSeconds can span multiple frames.
WaitForEndOfFrame resumes next frame after rendering.
Both help control timing in Unity coroutines.

Full Transcript

This visual execution shows how Unity coroutines pause and resume using WaitForSeconds and WaitForEndOfFrame. The coroutine starts and logs a message. Then it yields WaitForSeconds, pausing for 2 seconds real time before resuming and logging again. Next, it yields WaitForEndOfFrame, pausing until the current frame finishes rendering. After the frame ends, it resumes and logs a final message before ending. Variables track the coroutine state changing from not started, to waiting 2 seconds, to waiting end of frame, then completed. Key moments clarify that WaitForSeconds waits real time seconds, not frames, and WaitForEndOfFrame waits until the frame finishes. The quiz tests understanding of coroutine states and timing. This helps beginners see exactly when and why coroutines pause and resume in Unity.