For each of the 12 groups, predict the final standings (1st through 4th place).
Maximum per group: 15 points (5+3+2+5 bonus) | Maximum total: 180 points
Select the 8 third-place teams you predict will advance to the knockout stage.
Maximum: 16 points (8 × 2 pts)
Predict the winner of each knockout match. Points increase as the tournament progresses.
Maximum knockout points: 32+24+20+16+10+15 = 117 points
Group Stage (180) + Best Third (16) + Knockout (117)
Start by creating a prediction bracket from your dashboard. Give it a name to identify it.
For each of the 12 groups, predict how teams will finish. Tap teams in order — 1st, 2nd, 3rd, 4th — to set your predicted standings.
Choose which 8 of the 12 third-place teams will advance to the knockout stage. These are automatically assigned to Round of 32 slots based on their group.
Based on your group predictions, select winners for each knockout match from Round of 32 to the Final. Tap a team to advance them.
Compete with friends by joining groups. Share the invite code to add others.
All predictions must be submitted before the first match of the tournament begins (June 11, 2026). After the tournament starts, your bracket is locked and cannot be changed.
Yes! You can edit your predictions as many times as you like before the tournament starts. Just go to your bracket and make changes. They save automatically.
WC Predictor is free to use. You can create as many brackets and groups as you need; no paid upgrade is needed.
Groups let you compete with friends, family, or coworkers. Create a group and share the invite code, or join an existing group. Each group has its own leaderboard showing member rankings.
Scores are updated after each match is completed. Group stage standings scores are calculated once all group matches are finished. Leaderboards refresh automatically.
If users have the same total score, they share the same rank. In the future, we may add tiebreakers based on correct champion picks or correct final predictions.
Want to see the welcome guide again?
Found a bug or have an idea? Let us know.
Have a question not covered here? Found a bug? We'd love to hear from you.
Contact Support