MovieLens

On this page 7

MovieLens is a noncommercial movie recommendation website run by the GroupLens research lab at the University of Minnesota, and the name of the family of public rating datasets drawn from it. In Recommender systems research, the MovieLens datasets are the most widely used benchmark for explicit feedback, so the name usually refers to the data rather than to the website itself.

Each dataset records which users rated which movies, with star ratings, timestamps and, in later releases, free-text tags and genre labels. Because the data are real, stable and freely available for research, MovieLens became the common ground on which methods in artificial intelligence for recommendation, from collaborative filtering to neural ranking models, are compared.

How MovieLens collects rating data

MovieLens collects data through an ordinary recommendation service: users sign up, rate movies they have seen on a five-star scale, and receive personalized suggestions in return. The site launched in 1997, shortly after an earlier research service called EachMovie closed, and it has been used continuously since then as a live experimental platform for studies of interfaces, explanations and user behavior.

New members go through an onboarding step in which they rate a set of movies before recommendations appear. This design is the reason most released datasets include only users with at least 20 ratings, which makes the data denser than typical production logs. Since 2003, the interface has accepted half-star increments, so newer datasets use a scale from 0.5 to 5.0 in steps of 0.5, while the oldest releases use whole stars from 1 to 5.

The following table lists the main record types found in MovieLens releases and what researchers typically use them for.

Record typeMain fieldsTypical use
RatingsUser ID, movie ID, rating, timestampTraining and testing rating or ranking models
MoviesMovie ID, title with year, genresContent features and genre-aware models
TagsUser ID, movie ID, tag text, timestampFolksonomy and content-based studies
LinksMovie ID mapped to external movie identifiersJoining metadata such as plots or posters
Tag genomeMovie and tag relevance scores from 0 to 1Dense item descriptors and explanation research
Typical files and fields in MovieLens datasets

The main MovieLens dataset releases

GroupLens has published several fixed snapshots of different sizes, named mostly by their approximate number of ratings. A fixed snapshot never changes, which is what makes results comparable across papers; the “latest” releases, in contrast, are updated over time and are suitable for exploration but not for reproducible benchmarks.

ReleaseRatingsUsersMoviesNotable features
ML-100KAbout 100,000About 940About 1,700Whole stars, simple demographics
ML-1MAbout 1 millionAbout 6,000About 3,900Age, gender and occupation fields
ML-10MAbout 10 millionAbout 70,000About 10,700Half stars and user tags
ML-20MAbout 20 millionAbout 138,000About 27,000Tags, links and tag genome
ML-25MAbout 25 millionAbout 162,000About 62,000Extended tag genome
ML-32MAbout 32 millionAbout 200,000About 87,000Most recent large snapshot
Commonly used MovieLens releases with approximate sizes

Smaller releases such as ML-100K remain popular for teaching and quick experiments, because a model trains in seconds. Larger ones are preferred when a method must show that it scales to millions of interactions, although even ML-32M is small compared with industrial logs that contain billions of events.

Why MovieLens became a standard benchmark

MovieLens became a standard because it combines real user behavior, open access and stable versions, a rare mix in a field where most valuable data belong to companies. Before public datasets existed, each group evaluated on private data, so claims could not be verified. The Netflix Prize dataset later reached a larger audience, but its distribution was withdrawn over privacy concerns, which left MovieLens as the long-term reference point.

The datasets also suit many related tasks in recommendation research. Researchers use them for rating prediction, top-N recommendation, matrix factorization, cold start simulations, sequential recommendation with timestamps, and studies of popularity bias and diversity. The table compares MovieLens with other public data commonly used in the same studies.

DatasetFeedback typeDomainMain strengthMain weakness
MovieLensExplicit star ratingsMoviesStable, clean, well documentedDense and unlike production data
Netflix Prize dataExplicit star ratingsMoviesVery large for its timeNo longer officially distributed
Amazon review dataRatings and review textRetail productsMany categories and textExtremely sparse, noisy duplicates
Click and session logsImplicit feedbackE-commerce or newsClose to real ranking tasksOften short-lived or restricted
MovieLens compared with other public recommendation datasets

Using MovieLens correctly in experiments

Correct use of MovieLens starts with naming the exact release and the evaluation protocol, because results on ML-1M and ML-20M are not interchangeable. A reported score is meaningful only together with the data split, the metric and the candidate set used for ranking.

Many modern papers convert explicit ratings into implicit feedback, for example by treating every rated movie as a positive interaction or keeping only ratings of four stars and above. This conversion is legitimate, but it changes the task from predicting stars to predicting which movies a user chose to rate, and that difference must be stated. The decision table summarizes the most common protocol choices.

ChoiceRecommended optionReason
Data splitTime-based or leave-last-out per userRandom splits leak future information
Rating task metricRMSE or MAEMeasures error on the star scale
Ranking task metricRecall, NDCG or MAP at a fixed cutoffMatches how lists are shown to users
Candidate setFull catalog rankingSampled negatives can reverse model rankings
BaselinesTuned matrix factorization and popularityWeak baselines inflate reported gains
Protocol choices and their consequences

The data are released under terms that allow research use, require acknowledgment of GroupLens, and prohibit commercial use or redistribution without permission. Teams building products therefore use MovieLens for prototyping and method selection, not as training data for a commercial service.

Limitations and common mistakes with MovieLens

The biggest limitation is that MovieLens is not representative of production traffic. Its users are self-selected movie enthusiasts, every user has many ratings, and ratings were often entered in bursts during onboarding rather than after watching, so timestamps do not reflect viewing order.

  • Overreliance on one dataset: a method that wins on MovieLens may lose on sparse retail or news data.
  • Timestamp misreading: sequential models can learn rating sessions instead of real taste evolution.
  • Sampled evaluation: ranking the true item against 100 random negatives tends to overstate accuracy and can change which model looks best.
  • Version confusion: mixing results from different releases makes comparisons invalid.
  • Ignoring popularity effects: a simple most-popular list is a surprisingly strong baseline on these data.

Understanding it simply

MovieLens is a website where people rate films and get suggestions for what to watch next. The researchers who run it regularly publish the collected ratings, with names removed, so that anyone can test new recommendation ideas on the same real data.

Think of it as a shared practice exam for recommendation engines. Because everyone answers the same questions, it is easy to see whose method does better. The catch is that a practice exam is cleaner than real life, so a good MovieLens score is a promising sign, not a guarantee.

Applied in practice

A small data science team at a regional video streaming service wants to replace its genre-based suggestions with a learned model. Before touching its own logs, the team downloads ML-25M and compares a popularity baseline, alternating least squares and a two-tower neural model under a time-based split, measuring recall at 20 over the full catalog.

On MovieLens, the neural model beats matrix factorization by a clear margin, while both easily beat popularity. When the team repeats the same pipeline on three months of its own viewing data, the gap between the two learned models shrinks to almost nothing, because its catalog is smaller and most users watch only a few titles. The outcome is a faster, cheaper launch with matrix factorization, and MovieLens served its proper role: a safe place to build and debug the pipeline before the decisive test on real traffic.