about

A person built this, and here he is.

My name is Gustavo Cruz. I write the code for steamprofiler.org, I pay for the machine it runs on, and I am the one who answers when something here is broken. The site talks about itself in the first person on every page, and until now it never said whose person that was.

why it existsone picture

Steam knows exactly how many hours went into every game somebody owns, and shows it as a list sorted by a number. A list is the one shape that cannot answer the question people actually have about their own library, which is not "what is on top" but "what did all of it add up to".

So this site draws the library to scale instead: one rectangle per game, area proportional to hours. Thirteen years of a Steam account become one picture.

The rest of it grew out of that. Every game that was ever launched gets a page built out of that game’s own interface, because a shared template would have made a hundred and fifty-nine different games look like one spreadsheet.

is this safethe short answer

It is a fair question to ask of any site that wants a Steam profile, and the answer is in what this one never asks for.

You never sign in. There is no login, no OpenID, no Steam sign-in button, and nothing here can act on an account. Everything on this site is read from the profile Steam already publishes to anybody.
You never give me a key. The Steam API key is mine, it lives on my server, and it is why there is a backend at all - a key in the browser is a key given away.
Nothing here trades, sells or offers anything. No items, no skins, no gambling, no "verify your account". If you find a page on this domain doing any of that, it is not mine.
Nothing about you is kept. No account, no cookies, no trackers, no analytics profile. What a lookup produces lives in a cache for fifteen minutes and then it is gone - the privacy page is the long version.

Both halves of the site are public and MIT licensed: the front end ↗ and the service that reads Steam ↗.

how it is madefront + API

Two open-source parts make the site. The front end is static HTML, CSS and JavaScript, with no framework or build step. The API is a Python service that talks to Steam, shapes the public data and keeps short-lived caches. Both live in their own public, MIT-licensed repository.

It is a hobby project and it is built with AI assistance, reviewed and shipped by me. I would rather say that plainly here than have somebody work it out and wonder what else was not said.

where to find meand the site

steamprofiler.org is not affiliated with Valve. It is built on what Steam publishes, and it stops working the day Steam stops publishing it.