Good fit
- You need browser-side FFT with a real WebGPU path.
- You want clear API contracts and low package overhead.
- You care about documented GPU versus CPU boundaries.
This page is the shortest serious route through the project. Read it when you want to evaluate fit, boundaries, and next steps without wandering the whole docs tree.
Capability matrix
| Surface | GPU | CPU | Notes |
|---|---|---|---|
| 1D FFT / IFFT | Native | Fallback | Complex interleaved input contract |
| 1D RFFT / IRFFT | Wrapped | Native | Half-spectrum contract |
| 2D FFT / IFFT | Native | Fallback | Row-column decomposition |
| Spectrum analyzer | — | CPU only | Built on window functions and CPU FFT |
| Image filter | — | CPU only | Frequency-domain utility, not a GPU shader pipeline |
Good fit
Not a fit
| If you care most about | Read next |
|---|---|
| API shape and installation | Quick Start |
| Browser readiness | Browser Support |
| Architectural credibility | Architecture Overview |
| Performance honesty | Benchmarks |
| Research context | Academic Papers |