Pixel Peeker

Pixel Peeker is a browser-based tool for designing LED video walls and calculating processor port capacity.

  • Media Applications
  • Productivity
  • Tools & Utilities
Pixel Peeker is a browser-based tool for designing LED video walls and calculating processor port capacity. It plans walls from a cabinet library parsed from manufacturer datasheets, checks capacity against published NovaStar MX40 Pro and Brompton SX40 figures, and exports Resolume Arena layouts — letting designers plan and verify walls without installing local software.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

59/100 Fair

Maintained
100last commit 9 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 19 days ago

GitHub stars
3
Open issues
0
Last commit
2026-11-12
License
MIT
Activity
declining

Checked 6 days ago - source: GitHub (stoatworks-labs/pixel-peeker)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add your PixelPlus API token and project ID Before the app can work, enter your own PixelPlus API token and project ID in the settings, not the sample values. The token is a password that lets the app access your account, and the project ID tells it which project to read. source
  • Save the AI image/video API key separately If you use the AI image or video tools, save the API key from your PixelPlus account in the app settings. Without a valid key, the app will not be able to send or fetch generated images or videos. source
  • Keep date ranges in mind for competitor checks For competitor reports, make sure the start and end dates are set when you open the feature. The API expects a date range, so missing dates can cause empty or failed results. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Pixel Peeker run as a static self-hosted tool without a backend or accounts?

Yes. It runs entirely in the browser, requires no account or server, and can be deployed as a static site.

What should I do if the exact cabinet I need is not in the library?

Define a custom panel by resolution and receiving card, then use it in the layout.

How can I keep a design after closing the browser?

Export the versioned JSON interchange file. The app does not upload the design to a server.

What hardware and controller data does Pixel Peeker include?

It includes 150 cabinets across five manufacturers and 15 processors, each record taken from the maker's datasheet.

How much confidence should I place in its capacity results?

The capacity model is tested against published NovaStar and Brompton figures, but the project is alpha and has not been used to design a wall that was then built.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads