A Unity debugger that can call your own code, and no preprocessor key to strip it
Graphy is the ultimate, easy to use, feature packed FPS counter, stats monitor and debugger for your Unity project.
At a glance
- What is it?
- Graphy is an FPS counter and stats monitor for Unity, MIT licensed and free in the repository, with a debugger that fires consequences when conditions are met. Its roadmap lists a preprocessor key for excluding the asset from builds as planned with no date, so the README documents no way to exclude it from a build.
- Who is it for?
- Graphy suits a Unity developer who wants frame time, memory and audio on screen while building, and who will read the Editor and Runtime folders before shipping. Four things to check first.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 78 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Tayx94/graphy2,920 ★ · +13
| Repository | 2026-09-25 | 2026-11-15 |
|---|---|---|
| Tayx94/graphy | 2.9k | 2.9k |
13 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Five install routes, and one of them is a fallback for Unity 5.4
Installation is written as five numbered routes, and the differences between them matter. The first is the openupm registry through its command line tool.
openupm add com.tayx.graphyThe second adds the package through Unity's own Package Manager by declaring a scoped registry named package.openupm.com at the address https://package.openupm.com, with two scopes, com.openupm and com.tayx.graphy, after which the package appears under My Registry. The third skips the registry and points manifest.json at the git URL directly.
{
"dependencies": {
...
"com.tayx.graphy": "https://github.com/Tayx94/graphy.git",
...
}
}The fourth route is the Asset Store listing, and the fifth is a tagged old version, v1.6.0-Unity5.4, named for the editor it supports. That last one is the clearest statement of how wide the version spread is: a line for Unity 5.4 and newer, the 3.x line, and 4.0.0 for Unity 2022.3 and newer.
The 3.x line stood still for almost three years
The release history has two entries and then a gap. Graphy 3.0.4 was published 2023-11-09 and 3.0.5 followed six days later on 2023-11-15. The next tag is Graphy 4.0.0, published 2026-08-29, which is two years, nine months and fourteen days after the one before it. That release is also the last push to the repository, so the branch and the newest tag point at the same moment.
What changed in that jump is stated only in the release name, Graphy 4.0.0 - Unity 2022.3, and in the manifest field that accompanies it, a unity value of 2022.3. That field is the one that matters practically, because it is what the editor checks before it will resolve the package, and it is why the README states that Graphy works with Unity 2022.3 and newer. CHANGELOG.md sits at the repository root and the README never links it, so the details of a major version bump have to be read from the diff.
The debugger runs consequences when conditions are met
This is the part of the asset that is more than a readout. The debugger lets you set one or more conditions and decide what happens when they are met. The listed consequences are taking a screenshot, pausing the editor, and printing a message to the console, and the description ends by saying you can even call a method from your own code.
That last consequence is the one to think about. A debugger that can invoke arbitrary project methods on a condition is a small automation engine pointed at your own codebase, and its power depends entirely on what the conditions and the consequences are. Nothing in the README describes whether the conditions can fire in a release build as opposed to the editor, or how the two are distinguished. If you are profiling a build you ship, that distinction decides whether a screenshot or a method call can happen in front of a player.
The roadmap lists the build-time exclusion key as planned, with no date
The roadmap section is headed Planned features with no ETA attached, and the last entry on it decides what goes into your release. It proposes adding a preprocessor key, #GRAPHY, to avoid adding the asset in builds. Until that exists, the README documents no switch for keeping the asset out of builds.
The other four entries are equally concrete about what is missing. GfxDriver statistics are not in the RAM module yet. There is no template for creating a graph or text module, so a custom readout is written from scratch. FPS history is not stored for a predetermined window, which is why there is no built-in benchmark comparison. And dumping all Graphy data as a string is not implemented for a file, for a server, or for mail, even though the destinations are spelled out.
Editor and Runtime are separate folders, and meta files are committed for everything
The root of the repository is laid out the way a Unity package should be. Editor/ and Runtime/ are separate directories, each with its own .meta file, which is how editor-only code is kept from reaching a player build. Alongside them sit GUI/, Font/, Materials/, Prefab/, Shaders/ and Textures/, so the asset brings its own prefabs, shaders and font rather than depending on anything in your project.
What is unusual is the versioning of the meta files. Every Unity asset directory has one (.github/ does not), and so do files at the root that Unity does not import as assets: LICENSE.meta, README.md.meta, package.json.meta and CHANGELOG.md.meta. The documentation PDF is named with an exclamation mark after Readme, which is the convention for controlling import order in a project view, and it has a meta file of its own.
Free in the repository, sold on the Asset Store, donations requested
Three statements about cost sit close together in the documentation. Graphy is released under the MIT license. Graphy is free to use, with a request that you leave a donation if it helped you, and a PayPal link. And the same product has an Asset Store listing linked in the header, the links list and the installation routes, whose price this repository does not state.
So free describes the repository copy, and the Asset Store is a separate listing whose price and contents this repository does not state. The licence paragraph adds a personal note on top of the terms: attribution is not required, but the author would like to be told if the asset ends up in a project, by social post or email. That is a request rather than an obligation, and it is the only condition stated beyond MIT itself.
The Discord invite link in three places ends with a question mark
The Discord invite address in the README, https://discord.gg/2KgNEHK?, carries a trailing question mark after the invite code 2KgNEHK, and the same address appears in the badge row, the links line at the top, the contributing section and the contact section at the bottom.
The rest of the contact surface is intact and rather old in style: a mail address, a Twitter profile, the Asset Store page, the forum post announcing the release, a video teaser and a PayPal donation link. The one external claim with a date attached is the Unity Awards 2018 win for best development asset, which is eight years old now and the only verifiable-looking distinction in the file. The self-description repeated in the title, the manifest display name and the manifest description is the same superlative wording in all three places.
A single maintainer, a dev branch convention, and a Discord as the discussion forum
Graphy has one named maintainer and main developer, listed in the manifest as the author and in the README as maintainer and main developer, with the same name, email address and profile link in both places. Contributions are invited in the first person singular, and the guidance is specific in two ways worth noting: a large pull request is asked for on the dev branch rather than on the default one, and a feature request is asked for as a labelled GitHub issue rather than as a message.
That is a small project with a clear process, which cuts both ways. There is one person to review, so a large change queues behind their availability, and the dev branch convention means contributions land somewhere other than the branch the badges and the README links point at. The Discord invitation is offered as the venue for active discussion, and it is the link with the trailing question mark. The stated ambition in the contributing section is to make Graphy the go-to for stats monitoring in Unity, which is a goal rather than a status.
Editorial conclusion
Graphy suits a Unity developer who wants frame time, memory and audio on screen while building, and who will read the Editor and Runtime folders before shipping. Four things to check first. The asset has no preprocessor key yet, so decide yourself how it leaves a release build. The debugger can call a method from your own code when a condition is met, so treat its condition list as code and review it. Free in the repository does not mean free everywhere, since the same product is also listed on the Asset Store and donations are requested. And if you are on a Unity version below 2022.3, the manifest field in package.json will not resolve for you and the old 1.6.0 tag is the documented fallback.
Frequently asked questions
how to use graphy
There are five documented routes: add it from the openupm registry with `openupm add com.tayx.graphy`, declare the package.openupm.com scoped registry in Unity's Package Manager, point manifest.json at the git URL, install it from the Asset Store listing, or use the v1.6.0-Unity5.4 tag for old editors. Version 4.0.0 declares unity 2022.3 in its manifest.
is graphy free
The repository copy is free and MIT licensed, with an optional donation link. The same asset is also listed on the Unity Asset Store, and that listing's price is not stated in this repository. The documentation adds that attribution is not required but that the author would like to be told if you use it in a project.
What does the Graphy debugger do when a condition is met?
You set one or more conditions and choose the consequence: taking a screenshot, pausing the editor, printing a message to the console, or calling a method from your own code. The README does not describe whether these can fire in a release build as opposed to the editor.
Can Graphy be excluded from a release build?
Not by a documented switch. The roadmap lists adding a preprocessor key, #GRAPHY, to avoid adding the asset in builds, under planned features with no ETA. Editor and Runtime are separate folders in the repository, but no key or define is documented for stripping the asset from a player build.
How current is Graphy for Unity?
Version 4.0.0, named Graphy 4.0.0 - Unity 2022.3, was published 2026-08-29 and was also the last push to the repository. Before it, 3.0.5 dates from 2023-11-15, so the 3.x line stood for close to three years. The repository is not archived and a CHANGELOG.md exists at the root without being linked from the documentation.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tayx94-graphy)Star history chart for your README
[](https://hysenlabs.com/projects/tayx94-graphy)Was this useful?