Google Summer of Code 2026: Closed Contributor Applications and $750 to $6,600 Stipends

Google Summer of Code 2026: Closed Contributor Applications and $750 to $6,600 Stipends

Google Summer of Code (GSoC) 2026 is no longer accepting contributor applications. The official contributor application window opened on March 16, 2026 and closed at 18:00 UTC on March 31, 2026. Google has already announced the accepted 2026 projects, so this page is a historical reference rather than a live application opportunity. There is no verified 2027 application schedule on the official program pages checked for this update.

That status does not make the program irrelevant. GSoC remains one of the clearest ways for a student or newcomer to open source to work with an established community, receive guidance from experienced maintainers, and earn a stipend for a defined software project. The 2026 program page currently lists 184 mentoring organizations and 1,156 contributors with announced projects. Anyone preparing for a future round can use the 2026 rules and workflow as a concrete model, while checking the next official timeline for changes before relying on any dates or requirements.

Verified status of the 2026 cycle

The official timeline also records the later stages of the 2026 cycle. Accepted projects were announced on April 30, the community bonding period ran from May 1 through May 24, and coding officially began on May 25. For standard projects, the work period ran from July 6 through August 16, followed by final submissions and evaluations. Extended projects could continue into November, with the final contributor work-product deadline on November 2 and the final mentor evaluation deadline on November 9. These dates describe the completed 2026 intake and should not be treated as a new application window.

What GSoC is

GSoC is a global, online program that introduces new contributors to open-source software development. A contributor is matched with an accepted mentoring organization and works on a project under the guidance of mentors from that community. The work is expected to be useful to the host project, not merely a private exercise. The exact technical area depends on the organizations accepted for a given year: past and current lists have included developer tools, programming languages, science, medicine, infrastructure, security, web applications, and many other areas.

The program is not a Google job, Google internship, or employment relationship with Google. Participants are independent contributors receiving a stipend after passing the required evaluations and meeting payment eligibility requirements. The mentoring organization may adopt, revise, or decline the resulting code according to its own review process. A successful project can still provide valuable evidence of engineering ability because it shows how an applicant worked in a public repository, responded to review, communicated with maintainers, and completed a scoped deliverable.

The work is remote. The contributor and mentors agree on communication habits, milestones, and any time away needed during the project. A contributor may be working from home, a campus, or another location, but must be eligible to work in the country of residence and able to receive payment there. The program page and FAQ are the authority for country-specific restrictions and payment eligibility.

Stipend and project scope

The 2026 stipend is not one flat award. Google calculates the amount from the project size and the contributor’s location using a purchasing-power-parity adjustment. The official 2026 stipend table gives these overall bands:

• Small projects: $750 to $1,650, with an expected workload of about 90 hours.
• Medium projects: $1,500 to $3,300, with an expected workload of about 175 hours.
• Large projects: $3,000 to $6,600, with an expected workload of about 350 hours.

The exact amount depends on the country where the contributor resides during the coding period. A person should therefore consult the country table rather than assume that the largest number in the headline range applies to them. Google says that stipends are paid in two parts after successful evaluations. For the standard 12-week arrangement, the first payment is 45% and the final payment is 55%; a longer project uses its own evaluation schedule.

The hours are planning guidance, not permission to promise an unlimited feature list. A good proposal turns the selected project idea into a small set of measurable outcomes. It identifies the code or documentation that will change, explains how the contributor will test the work, and separates essential deliverables from optional stretch goals. The FAQ also says that the contributor and mentor can adjust scope if the project turns out to be too large or too small. That conversation should happen early, before a missed milestone becomes a crisis.

Eligibility for the 2026 model

The official FAQ lists the core contributor requirements. An applicant had to be at least 18 years old at registration, be eligible to work in the country of residence, and either be a student or a beginner in open-source development. The applicant could not reside in a U.S.-embargoed country and could not have been accepted into GSoC more than once previously.

“Beginner” refers to open-source experience, not necessarily programming ability. Google says that personal or class projects, including boot-camp work, do not by themselves prevent someone from being considered a beginner. A small number of issues or pull requests against open-source packages can also fit that definition. Regular contributors to an established open-source project generally do not qualify as beginners. Professional engineers are not automatically excluded, but the program is aimed at newcomers and the expected time commitment may be difficult to balance with a full-time role.

The rules also matter for people who do qualify. Proposals must be submitted by individuals, not teams. Applicants may submit up to three proposals, but only one can be accepted. Google’s advice recommends focusing on one or two strong proposals instead of treating the process as a numbers contest. An organization’s own requirements can add detail, such as a preferred proposal format, required technical background, communication channel, or contribution expectation. Those organization-specific instructions are part of the application process.

How the 2026 application process worked

The application route is closed for 2026, so nobody should attempt to submit a late proposal or treat this page as a way around the deadline. Google’s advice states that extensions are not available. The process below is useful for understanding the completed cycle and preparing for a future official window:

1. Read the program site, rules, FAQ, timeline, and contributor guidance. Confirm the current year’s eligibility, project sizes, payment rules, and submission instructions.
2. Browse the accepted mentoring organizations and their project ideas. Google recommends researching several organizations in areas that match the applicant’s interests, skills, and preferred tools.
3. Visit the organization’s repositories, documentation, issue tracker, mailing list, or chat channel. The goal is to understand how the community works and whether the proposed project is a good fit.
4. Narrow the list to one or two serious options and contact the organization before writing the final proposal. Google specifically encourages applicants to discuss the idea with mentors and learn what the project needs.
5. Make a small, relevant contribution when feasible. Filing a useful bug report, improving documentation, adding a test, or submitting a focused patch can show that the applicant has set up the project and can work within its review process. It is not a universal guarantee of acceptance, but it produces better evidence than a generic statement of interest.
6. Write the proposal around detailed goals, a technical method, a clear schedule, testing, documentation, risks, and communication. Use the organization’s required format and explain what will be delivered at each milestone.
7. Submit through the official GSoC site before the published deadline. Do not send the proposal directly to an organization as a substitute for the program submission. For 2026, the official deadline was March 31 at 18:00 UTC.

Because the next cycle has not been announced on the checked official pages, future applicants should not copy the 2026 date into a calendar as if it were confirmed. The dates above are a record of the 2026 process. The next official timeline may shift, and the list of mentoring organizations, project ideas, payment table, and application instructions may change.

What makes a proposal credible

A credible proposal is specific enough that a mentor can imagine reviewing the work. Start with the problem: who has the problem, where it appears in the existing project, and why it is worth solving now. Then describe the proposed result in terms of repository changes, user-visible behavior, API changes, documentation, tests, or other observable outputs.

The schedule should match the project size. A small project should not contain a long list of unrelated features. A medium or large project can have several milestones, but each milestone needs an outcome that can be reviewed independently. Include time for reading the codebase, confirming design choices, writing tests, handling review, and documenting the finished work. The final weeks should not be the first time the contributor plans to integrate the result.

Communication deserves its own section. State how progress will be reported, how often the contributor expects to speak with the mentor, and what will happen when a blocker appears. A useful update can be simple: completed work, next work, and current blocker. Mentors need early notice when scope or availability changes. A proposal that acknowledges uncertainty and explains how decisions will be made is more useful than one that claims every detail is already known.

Applicants should also follow the organization’s authorship rules. The FAQ warns that an organization may reject AI-generated proposal text or code under its own policy. The final proposal should be the applicant’s original work, technically accurate, and consistent with the community’s standards. If an organization asks for a contribution, design discussion, or specific proposal template, follow that instruction rather than relying on a generic application document.

What to do now

There is no live 2026 submission step remaining. A reader finding this page should use the official 2026 program page to review the announced organizations and projects, understand the completed timeline, and distinguish the coding program from the closed contributor intake. Someone preparing for a future cycle can study the communities that interest them, build one or two small open-source contributions, and keep notes on the problems they may want to propose.

Before treating any future GSoC listing as open, verify three things on Google’s official pages: the current program year, the contributor application dates, and the organization’s own project instructions. Confirm the eligibility rules and the stipend table for that year as well. This page deliberately keeps the real 2026 deadline in its metadata and marks the entry as historical so that the archive is useful without pretending that applications are still being accepted.

Official references:

• GSoC 2026 program details
• GSoC timeline
• GSoC frequently asked questions
• Contributor stipends for 2026
• Advice for people applying for GSoC