AlphaGo Fan

Closed weights DeepMind 8.2M parameters October 2015

No estimate

No hardware requirements for this model

The weights for this model have not been published, so it cannot be downloaded or run on your own hardware at any size. It is reachable only through its provider, and no graphics card changes that.

On record

Full specification

Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.

Origin

Who built this model, where, and when it was published.

Organisation
DeepMind
Organisation type
Industry
Country
United Kingdom of Great Britain and Northern Ireland
Published
1 October 2015
Authors
David Silver, Aja Huang, Chris J. Maddison, Arthur Guez, Laurent Sifre, George van den Driessche, Julian Schrittwieser, Ioannis Antonoglou, Veda Panneershelvam, Marc Lanctot, Sander Dieleman, Dominik Grewe, John Nham, Nal Kalchbrenner, Ilya Sutskever, Timothy Lillicrap, Madeleine Leach, Koray Kavukcuoglu, Thore Graepel, Demis Hassabis

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Games
Task
Go

Size

How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.

Parameters
8.2M

The input to the policy network is a 19 × 19 × 48 image stack consisting of 48 feature planes. The first hidden layer zero pads the input into a 23 × 23 image, then convolves k filters of kernel size 5 × 5 with stride 1 with the input image and applies a rectifier nonlinearity. Each of the subsequent hidden layers 2 to 12 zero pads the respective previous hidden layer into a 21 × 21 image, then convolves k filters of kernel size 3 × 3 with stride 1, again followed by a rectifier nonlinearity. Th…

Training data
12,697,600,000 tokens

Supervised learning + self-play

Training compute

The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.

Training compute
3.8 × 10²⁰ FLOP

Assume 0.3 utilisation rate, 1e13 GPU FLOP/s [single precision]. Trained in three stages using 50 GPUs over 3 weeks + 1 day + 1 week Training compute = (50 GPUs)(29 days)(86400s/day)(0.3 utilisation rate)(1e13 FLOP/s) = 3.8e20 FLOPs

How it was established
Hardware

The training run

What it physically took to train: which chips, how many, for how long, and what that drew from the wall.

Compute cost
$4,828

Availability

Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.

Weights
Closed — provider access only
Model access
Unreleased
Training code
Unreleased

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Frontier model
Yes
Why it is tracked
Highly cited,SOTA improvement
Record confidence
Likely
Citations
18,175

Sources

Where this record came from and when it was last checked.

Reference
Mastering the game of Go with deep neural networks and tree search
Last updated
1 January 2026

What the numbers mean

Where it came from

AlphaGo Fan was published by DeepMind, in the country recorded as United Kingdom of Great Britain and Northern Ireland, during October 2015. It comes out of an organisation categorised as industry.

It works in the domain of Games, and is recorded as performing the task of go.

Its weights were never published, so it can only be reached through its provider. No graphics card changes that.

Training and provenance

The training run consumed about 3.8 × 10²⁰ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 12,697,600,000 tokens of text.

Its inclusion criterion: highly cited,SOTA improvement.

Answers

AlphaGo Fan — common questions

01

AlphaGo Fan— how much compute was used to train it?

Training consumed around 3.8 × 10²⁰ FLOP. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.

02

AlphaGo Fan— what GPU do I need to run it?

None. This is a closed model — its weights were never published, so it cannot be downloaded or run on your own hardware at any price. It is reachable only through its provider.

03

AlphaGo Fan— is it open source?

No. Its weights have not been published, so it exists only as a service controlled by its owner.

04

AlphaGo Fan— how many parameters does it have?

It has a parameter count of 8.2M. The input to the policy network is a 19 × 19 × 48 image stack consisting of 48 feature planes. The first hidden layer zero pads the input into a 23 × 23 image, then convolves k filters of kernel size 5 × 5 with stride 1 with the input image and applies a rectifier nonlinearity. Each of the subsequent hidden layers 2 to 12 zero pads the respective previous hidden layer into a 21 × 21 image, then convolves k filters of kernel size 3 × 3 with stride 1, again followed by a rectifier nonlinearity. The final layer convolves 1 filter of kernel size 1 × 1 with stride 1, with a different bias for each position, and applies a softmax function. The match version of AlphaGo used k = 192 filters; Fig. 2b and Extended Data Table 3 additionally show the results of training with k = 128, 256 and 384 filters. The input to the value network is also a 19 × 19 × 48 image stack, with an additional binary feature plane describing the current colour to play. Hidden layers 2 to 11 are identical to the policy network, hidden layer 12 is an additional convolution layer, hidden layer 13 convolves 1 filter of kernel size 1 × 1 with stride 1, and hidden layer 14 is a fully connected linear layer with 256 rectifier units. The output layer is a fully connected linear layer with a single tanh unit. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.

05

AlphaGo Fan— who created it?

It was published by DeepMind, based in United Kingdom of Great Britain and Northern Ireland, an organisation categorised as industry.

06

AlphaGo Fan— when was it released?

It was published in October 2015. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

07

AlphaGo Fan— what is it used for?

It works in the domain of Games, and is recorded as handling the task of go. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.

Source

Original publication

Record last updated 1 January 2026

The other direction

Looking at it from the other side?

This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.