> For the complete documentation index, see [llms.txt](https://docs.animeoshi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.animeoshi.com/core-concepts/oshimeter.md).

# What is the OshiMeter?

## In one sentence

The OshiMeter is AnimeOshi's per-episode rating score, aggregated from individual fan star ratings and the five Rating Attributes that fans submit on each episode.

## Overview

The OshiMeter is the headline number you see on every AnimeOshi episode page. It exists because giving a single overall score to an entire anime hides how much episode-to-episode quality actually varies. A long-running shounen might have peak-tier arcs and weak filler stretches under the same series average. The OshiMeter measures each episode on its own terms and presents the result as a number you can read at a glance.

## Details

### How the OshiMeter is built

Every rating an AnimeOshi user submits on an episode contributes to that episode's OshiMeter. A rating consists of:

* A **1–10 star score** on the episode overall.
* Optional scores on the five **Rating Attributes**: Soundtrack, Visual, Emotion, Writing, and Impact.

The OshiMeter aggregates those submissions into a single per-episode score, stored internally on a 0–100 scale. The attribute averages are surfaced separately as a five-axis radar on the episode page, so the *shape* of the score (whether was it the music, the writing, the visuals?) is visible at a glance.

### How the score is displayed

The OshiMeter shows up in three ways across the site:

| Display                      | Looks like                                              | Where you see it                                       |
| ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------ |
| **0–10 with one decimal**    | `9.1`                                                   | Episode and anime detail pages, search results, embeds |
| **Percentage**               | `91%`, often phrased as "91% recommended by 1,375 fans" | Marketing surfaces and some episode page contexts      |
| **Score band (color-coded)** | red (0–59) / pink (60–79) / neon green (80–100)         | Episode guide blocks on each anime page                |

The underlying number is the same; the format changes based on the context.

### How to read an OshiMeter score

A higher OshiMeter means more fans judged the episode as standout. The bands are tuned so that:

* **High-scoring (80–100)** episodes are the ones worth prioritizing: arcs, peaks, finales, standout one-offs.
* **Mid-range (60–79)** episodes are watchable but unremarkable; fine if you're following the series, easy to skip if you're cherry-picking.
* **Low-scoring (0–59)** episodes are the filler / off-week / dropped-the-ball ones that an aggregate show score normally hides.

A 9.0 OshiMeter is uncommon, as those tend to be the episodes anime fans remember by name, not by number.

### How the OshiMeter differs from MyAnimeList or AniList scores

| Dimension      | OshiMeter                                                    | MyAnimeList / AniList                  |
| -------------- | ------------------------------------------------------------ | -------------------------------------- |
| Granularity    | Per episode                                                  | Per series                             |
| Inputs         | 1–10 star rating **+** five attribute scores per fan         | One overall score per user per series  |
| Output         | A single per-episode number plus a five-axis attribute radar | A single per-series number             |
| Watch decision | A per-episode OshiMeter score + color band                   | Implicit, based on the aggregate score |

These platforms answer ***"Is this anime good overall?"*** The OshiMeter answers, ***"which episodes of this anime are actually worth my time?"***

## FAQ

**Q: How is the OshiMeter score calculated?**

Every fan who rates an episode contributes a 1–10 star score (and optionally scores on the five Rating Attributes). The OshiMeter aggregates those submissions into a single per-episode number, stored on a 0–100 scale and shown as either a 0–10 score or a percentage.

**Q: What is considered a good OshiMeter score?**

Scores of 80 and above (an 8.0 out of 10) fall into the top color band and mark the episodes most worth prioritizing. A 9.0 is uncommon and tends to flag standout episodes; arc peaks, finales, or unforgettable one-offs.

**Q: Is the OshiMeter per episode or per show?**

Per episode. Every episode on AnimeOshi has its own OshiMeter. There is no single show-level OshiMeter — that aggregation is intentionally avoided because it flattens the very episode-to-episode variation the OshiMeter is built to surface.

**Q: Why does the OshiMeter sometimes look like 9.1 and sometimes like 91%?**

They are the same number in two formats. AnimeOshi stores the OshiMeter internally on a 0–100 scale and most often displays it as a 0–10 number with one decimal. Marketing surfaces and some episode contexts use the percentage form ("91% recommended by 1,375 fans") because that phrasing reads more clearly outside the episode page.

## Related pages

* [What are AnimeOshi Rating Attributes?](/how-rating-works/rating-attributes.md)
* [Watch If / Skip If](/core-concepts/watch-if-skip-if.md)
* [How to Rate Episodes on AnimeOshi](/how-rating-works/how-to-rate-episodes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.animeoshi.com/core-concepts/oshimeter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.