paper-design/shaders

Zero-dependency canvas shaders that can be installed from npm or designed in Paper

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 20th, 2026
Created on October 9th, 2024
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 152
Total Stargazers: 3,463 (+0)
Total Subscribers: 10 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 275 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Paper Shaders is a zero-dependency canvas shader library that can be installed from npm or designed visually in Paper.

The tool solves the problem of adding textured, animated visual effects to web applications without requiring complex WebGL knowledge or heavy dependencies. It provides pre-built shaders that run on HTML canvas and can be customized through a visual designer. Designers can create shaders visually and export them as lightweight, ready-to-use code that integrates directly into any codebase.

The library suits projects where visual polish matters but bundle size and performance are constraints. It works as a background layer or masked with shapes and text, making it useful for hero sections, landing pages, and design-forward interfaces. The tool emphasizes maximum performance and visual quality while keeping abstractions simple enough for designers to experiment with. Vanilla JavaScript and React are supported through separate npm packages, with Vue and other frameworks open to community contributions.

Development shows consistent maintenance with a structured release process using semantic versioning and a documented changelog. The project uses a monorepo structure with separate packages for different framework integrations, managed through a build and publish workflow. The maintainers have established clear licensing terms that permit commercial use without attribution while requiring credit preservation if the code is redistributed as part of another library.