Unity Official Game Jam Submission Worksheet Before November 14 - 2026

If you searched unity game jam submission after joining the Official 2026 Unity Game Jam, you do not need another “make something cool this week” poster. You need a fill-in submission worksheet that forces a Buffer freeze date, a playable Unity build on itch (with WebGL marked playable in the browser when you want prize eligibility), page fields judges can read without Discord archaeology, GenAI disclosure if you used it, and a signed SUBMIT_OK before Saturday, November 14, 2026, 12:00 UTC.

Unity hosts the Official 2026 Unity Game Jam on itch. Kickoff and theme reveal land on Thursday, November 5 (livestream ~17:00 UTC / theme near 18:00 UTC per staff notes). You get seven full build days, then The Buffer™ — extra time to package, upload, design the submission page, and fix whatever breaks in the build. Unity’s jam page is explicit: do not use Buffer to keep adding features, and late submissions will not be accepted. Staff on Unity Discussions add the prize gate many teams still miss: a WebGL build that plays in the browser on itch is required to be judged for prizes. Official Web platform build guidance lives in Unity’s Build and distribute a Web application docs.

This URL is the submit evening lab. It is not a theme-brainstorm thread. It is not a Unity Editor beginner course. It is not the Epic AI MegaJam submission worksheet (different host, different cliff, Unreal/UEFN artifacts). It is not the Unity 6.6 WebGPU browser worksheet (production WebGPU enable lab). Those own other intents. This URL owns the Official Unity Game Jam fill-in submission receipt.

Why this matters now

Thousands of jam joiners (the itch page showed 2,494 Joined when research evidence was collected on 2026-11-04, and the live jam page continued climbing afterward) will still be adding “one more mechanic” on Buffer day with no WebGL upload, no controls text, no credit list, and no local-time conversion of 12:00 UTC. The failure mode is classic: theme-day heroics, Buffer treated as a second jam week, first WebGL build attempted at T−40 minutes, upload fails, cliff hits, no late entry.

Direct answer: Before you call the jam “submitted,” fill Sections A–J. Green means itch jam submit is complete with artifacts players and judges can open. Red means HOLD — freeze content, finish WebGL, fill page fields, or fix the form. Treat November 14, 12:00 UTC as a hard cliff. Re-read the itch jam page the morning you submit — prize tables and Official Rules can update.

Who fills this worksheet

Time: 90–180 minutes for first dry-run mid-jam; 45–90 minutes for final Buffer evening if dry-run passed.
Honest limit: The itch jam page + Official Rules are authorities. This worksheet summarizes submit mechanics — if itch and this page disagree, itch wins. Coverage of the jam also appears on 80.lv; still verify against itch before you ship.

Non-repetition

Official facts you must quote (not invent)

From the Official 2026 Unity Game Jam page and Unity staff posts:

1. Kickoff livestream Thursday, November 5, 2026 (~12 PM EST / 9 AM PST / 17:00 UTC); theme revealed near the end (~18:00 UTC per Discussions).
2. Seven days to build; then Buffer time to package/upload/page/fix.
3. Submission deadline Saturday, November 14, 2026, 12:00 UTC — no late submissions.
4. Teams 1–5 people; one submission per team.
5. Games must be created in the Unity engine; submit through the itch jam page.
6. Submission page should include a playable build, short description, controls, credit list for all assets, and team members.
7. Mark your WebGL build as playable in the browser on itch. Staff: WebGL browser play is required to be judged for prizes.
8. For web builds, Unity target is the Web platform (publishes as WebGL); graphics API may be WebGL or WebGPU, but the uploaded build must run in the browser on itch.
9. You can update your submission until the deadline — submit early and update; do not wait.
10. After the jam ends / during judging, do not update game files in-engine or via servers; post-deadline updates can remove you from voting.
11. Generative AI is allowed if disclosed on the submission page; failure to disclose can DQ prize categories.
12. Community rating November 14–21, 2026; Unity special prize judging November 14 – December 7, 2026; results livestream December 10, 2026.
13. Prize lanes include Unity Choice Awards (1st/2nd/3rd) and Best Student Game (all members need valid Unity Student Plan licenses).
14. Your game should be playable via the itch project page — off-itch build links can DQ.
15. Buffer length varies by timezone; everyone gets seven build days plus at least ~1.5 days after.

Pasteable diligence line:

We ran an Official Unity Game Jam submission worksheet: locked Buffer freeze, shipped a browser-playable WebGL build on itch with description/controls/credits/roster, disclosed GenAI if used, dry-ran upload before Nov 14 12:00 UTC, and signed SUBMIT_OK (or HOLD with owner).

Section A — Submit lock (fill in)

A-gate: If cliff local time is blank, stop. If Official Rules unread, stop. If submit owner is “whoever is awake,” assign a name. If student claim = Y, confirm every member has a valid Student Plan before you fill marketing copy.

Beginner first path (twenty minutes)

1. Convert 12:00 UTC on Nov 14 to your wall clock.
2. Name the submit owner.
3. Circle prize intent (community fun vs Unity panel).
4. Fill Section A + B.
5. Do not start a final WebGL cook until B-gate is green and content freeze is written in Section C.

Section B — Eligibility + team roster

B-gate: Every seat has a name. Empty seats are not “TBD at submit.” Best Student claims need all members licensed — one missing Student Plan fails the category even if the game is great.

Company note: Roster names and Student Plan claims are diligence artifacts — treat them like partner contacts, not Discord nicknames.

Section C — Buffer freeze (content stop)

Unity recommends finishing the game by midnight at the end of your seventh jam day, then using Buffer for package, upload, page design, and build fixes — not new features.

Buffer timezone cheat sheet (from itch)

C-gate: Content freeze is a timestamp with an owner, not a vibe. If someone is still “adding a boss,” you are not in Buffer — you are still jamming into the cliff.

Creator Discord paste: “Buffer is package/upload/page/fix. Feature freeze is already signed.”

Section D — Playable build + WebGL prize gate

D-gate: If prize intent is Unity panel, browser-playable WebGL must PASS. Community-only entries can ship other playable builds, but you still need a playable build on the page. Staff rule of thumb from Discussions: test WebGL early so the deadline does not catch you.

Official path: install Web Build Support, switch Build Profiles to Web, build, upload, mark playable in browser. See Unity’s Web build distribution manual. For jam scoping while frames hold up, skim the Unity performance profiling guide. For production WebGPU experiments outside this jam, use the WebGPU worksheet — do not confuse that lab with prize eligibility tonight.

Dev tip: First WebGL cook mid-week with a thin scene. Final Buffer cook should be incremental, not “learn IL2CPP stripping at 10:00 UTC.”

Section E — itch page fields (judges and raters)

E-gate: Description + controls + credits + roster are not optional flavor. Missing controls text burns community ratings. Missing GenAI disclosure risks prize DQ even if the build is perfect.

GenAI disclosure mini-template

If GenAI = Y, paste something honest:

Generative AI used for: ____ (art / code assist / audio / writing). Tools: ____. Human authorship of final design: ____.

If GenAI = N, write NONE so nobody “forgets” later.

Section F — itch upload + jam submit mechanics

F-gate: Confirmation screenshot filed. “Upload started” without confirmation is not SUBMIT_OK. Prefer submit early + update over a single heroic upload at T−20.

Dev path: Dry-run upload mid-jam with a placeholder WebGL or tiny page so Buffer evening is not the first time you meet itch file limits and browser flags.

Section G — Judging path honesty

G-gate: Do not claim Best Student without licenses. Do not claim prize panel intent without WebGL browser smoke. Community rating still expects a playable itch page.

Section H — Post-deadline freeze (after 12:00 UTC)

H-gate: The jam page removes games that update after the deadline from voting. Your “hot patch” instinct is a DQ path here.

Section I — Pre-submit refuse ladder

Fail I3–I7 and you do not get to tweet “we submitted” while WebGL is still cooking.

Section J — Decision latch + receipt

RECEIPT: UNITY_OFFICIAL_GAME_JAM_SUBMISSION_WORKSHEET_v1
date: ________
team: ________
cliff_utc: 2026-11-14T12:00:00Z
cliff_local: ________
content_freeze: ________
webgl_browser_play: PASS/FAIL/N_A_community_only
page_fields_complete_y_n: ________
genai_disclosed_or_none: ________
itch_confirm_screenshot: ________
i_ladder_pass_y_n: ________
decision: SUBMIT_OK / HOLD / WITHDRAW
owner_sign: ________
notes: ________

Latch SUBMIT_OK only when A–F gates are green and I1–I9 pass. Latch HOLD with a named blocker (WebGL fail, missing credits, freeze unsigned). Latch WITHDRAW if eligibility breaks — do not ghost a half-upload.

Beginner path — Buffer evening order

Prerequisites: joined the jam on itch; Unity project playable enough to ship; Web module installed if chasing prizes. Skim the Unity guide hub if Build Profiles vocabulary is new. Paste Discord updates via communities in the 25 Discords resource.

1. Fill Section A — cliff in local time.
2. Fill Section B — roster (+ Student Plan honesty).
3. Sign Section C content freeze.
4. Complete Section D WebGL browser smoke (or explicit community-only).
5. Fill Section E page fields + GenAI line.
6. Upload + jam submit (Section F) with ≥90 minutes buffer — prefer early submit earlier in Buffer.
7. Run I ladder; sign Section J.
8. Paste Discord: “SUBMIT_OK — WebGL/page fields/form done; feature freeze holds.”
9. After cliff, obey Section H — no silent live patches.
10. Archive receipt + screenshots + build hash in the team drive.

Common beginner mistakes: treating Buffer as feature week; first WebGL attempt at T−40; forgetting “playable in browser”; empty controls/credits; GenAI with no disclosure; starting itch upload at 11:50 UTC; dual “we’ll also ship a desktop-only prize entry” folklore when panel rules need WebGL.

Developer path — mid-jam dry-run

1. Install Web Build Support on day one of the jam (or before kickoff).
2. Switch Build Profiles to Web once; note cook time on a thin scene.
3. Upload a draft WebGL to a private itch project mid-week; tick browser-playable; smoke in two browsers.
4. Measure download size; strip, compress, or cut content before Buffer — see Unity Web optimization notes in the Web distribution docs.
5. Keep a submit runbook: freeze → Web cook → browser smoke → page fields → jam submit → screenshot → tag hash.
6. Clock discipline: content freeze end of day 7; first real submit early in Buffer; final polish updates until cliff; stop engine pushes after cliff.
7. If shaders are cooking forever on Windows profiles, that is a different problem — see Unity shader build settings — but do not start a DXC rabbit hole on Buffer evening.
8. Log Asset Store / third-party attributions in the itch credits field as you add them.
9. Plan community rating queue: you may need to rate other games before free rating — budget time after submit.
10. After SUBMIT_OK, write a one-paragraph postmortem for Dec 10 results stream storytelling.

Creator Monday checklist

• [ ] Cliff converted to local time and pinned in Discord.
• [ ] Submit owner named.
• [ ] Buffer = package/upload/page/fix (not features).
• [ ] Content freeze timestamp signed.
• [ ] WebGL browser play PASS or community-only explicit.
• [ ] Description, controls, credits, roster filled.
• [ ] GenAI disclosed or NONE.
• [ ] itch confirmation screenshot filed.
• [ ] SUBMIT_OK signed or HOLD named.
• [ ] Post-deadline update ban pasted to the channel.
• [ ] Sibling MegaJam worksheet not confused with this cliff.
• [ ] Feature freeze holds after submit.

Failure modes

CapEx four-liner (diligence zip cover)

1. Scope — Official Unity Game Jam entry artifacts complete before Nov 14 12:00 UTC: playable itch build (WebGL browser for prize path) + page fields + GenAI disclosure + confirmation.
2. Cost — mid-jam Web dry-run evening vs cliff DQ / missing browser build.
3. Evidence — worksheet A–J + screenshots + build hash.
4. Owner — named submit lead who refuses LATE_SUBMIT and Buffer-as-features folklore.

Worked example — three-person WebGL prize path

Team of three, 2D puzzle game, chasing Unity Choice eligibility.

1. A: submit owner = lead designer; cliff pinned as local 07:00 / 13:00 / etc.
2. B: three names; not claiming Best Student.
3. C: freeze Nov 12 local midnight; Buffer reserved for Web cook + page.
4. D: Web profile build; itch browser-playable PASS in Chrome + Firefox.
5. E: controls card, asset credits, GenAI = NONE.
6. F: first submit morning of Buffer; two updates for bugfixes; final screenshot at T−2h.
7. H + J: SUBMIT_OK; git tag unity-jam-2026-submit.

Worked example — solo student desktop + WebGL

Solo student, Best Student intent, audio-heavy prototype.

1. A: Student claim Y; cliff local written.
2. B: Student Plan license confirmed.
3. C: freeze early because Web cook historically slow.
4. D: desktop build for friends and WebGL for prize eligibility; browser smoke PASS.
5. E: GenAI art assist disclosed in one paragraph.
6. F: early submit; update only page text during Buffer.
7. J: SUBMIT_OK; no live server swaps after cliff.

Opinion spine — what the worksheet forces

Quotable takeaway: Fill the Unity Official Game Jam submission worksheet before November 14 12:00 UTC. Buffer is not a second jam — freeze, WebGL, page fields, SUBMIT_OK.

How Buffer and the cliff interact (decision table)

Page field quality bar (so raters do not bounce)

WebGL smoke checklist (ten minutes)

1. Build Profiles → Web → Build.
2. Upload zip/folder to itch.
3. Enable This file will be played in the browser.
4. Open the itch page in a clean profile.
5. Confirm canvas loads, input works, audio policy OK.
6. Test one second browser if teammates use it.
7. Note load time; cut if Buffer cannot fix.
8. Record PASS/FAIL on Section D.
9. If FAIL and prize intent = panel, HOLD — do not fake SUBMIT_OK.
10. If PASS, proceed to page fields and jam submit.

Scheduling worked calendar (UTC spine)

Convert every row to local time in Section A. Awkward cliff hours (for example early morning US Pacific) are intentional — Unity says treat them as close of window, not a work target.

Internal links for the rest of your stack

If you need Editor fundamentals after the jam, start at the Unity guide hub. If jam cook times hurt, the shader settings posts help next project — not Buffer night. If someone pastes the MegaJam Nov 15 cliff into this Discord, send them back here and keep MegaJam’s own worksheet for that event. Help fixes live under /help/. Longer learning paths sit under /courses.

Key takeaways

1. Cliff: Nov 14, 2026, 12:00 UTC — late submits refused.
2. Buffer is for package / upload / page / fix — not new features.
3. Teams 1–5, one submission, Unity engine only.
4. Page needs playable build + description + controls + credits + roster.
5. Prize panel path needs WebGL playable in the browser on itch.
6. Submit early and update; do not wait for a single cliff upload.
7. Disclose GenAI or write NONE.
8. No post-deadline game file / server updates during judging.
9. Best Student needs all members on Student Plan.
10. Mid-jam Web dry-run beats Buffer panic.
11. Sign UNITY_OFFICIAL_GAME_JAM_SUBMISSION_WORKSHEET_v1.
12. CapEx four-liner belongs in the diligence zip.
13. Re-read itch Official Rules the morning you submit.
14. Quotable: Buffer is not a second jam — freeze, WebGL, SUBMIT_OK.
15. Dec 10 results storytelling needs a clean tagged snapshot.

FAQ

When is the Official Unity Game Jam submission deadline?

Saturday, November 14, 2026, at 12:00 UTC. Late submissions are not accepted.

What is The Buffer™?

Extra time after seven build days to package, upload, design your itch page, and fix build breaks. Unity asks you not to use it for new features.

Do I need a WebGL build?

For Unity prize panel eligibility, staff say you need a WebGL build that plays in the browser on itch. Community play still benefits from browser builds even if you are not chasing prizes.

What must the itch submission page include?

A playable build, a short description, controls, a credit list for all assets, and your team members.

Can I update after I submit?

Yes until the deadline. Submit early and update. After the deadline, do not update game files during judging.

Can I use generative AI?

Yes if you disclose how it was used on the submission page. Failure to disclose can disqualify prize categories.

How big can the team be?

One to five people, one submission per team.

When are winners announced?

Results livestream is scheduled for December 10, 2026. Community rating runs November 14–21; Unity special judging runs November 14 through December 7.

Is this the same as the Epic AI MegaJam worksheet?

No. MegaJam is a different jam with a November 15 PST cliff and Unreal/UEFN artifacts. Use that worksheet only for MegaJam.

Where do I join and submit?

https://itch.io/jam/official-unity-game-jam-2026

What if my WebGL build fails at the last hour?

That is why the worksheet demands a mid-jam dry-run. If prize intent requires WebGL and it fails, latch HOLD — do not pretend SUBMIT_OK.

Can voters download builds from Google Drive instead of itch?

The jam page wants play via the itch project page. Off-itch build links risk disqualification.

Sources

• Official 2026 Unity Game Jam (itch.io)
• The 2026 Official Unity Game Jam starts November 5th (Unity Discussions staff)
• Unity Invites Developers to Its 2026 Game Jam (80.lv)
• Build and distribute a Web application (Unity docs)