gpufft (Python)
Cross-vendor GPU FFT for Python. One API over two battle-tested libraries:
- cuFFT on NVIDIA (
backend="cuda") - VkFFT on any Vulkan device (
backend="vulkan"): AMD, Intel, Apple Silicon (MoltenVK), NVIDIA
pip install gpufft
import numpy as np
import gpufft
x = (np.random.randn(4096) + 1j * np.random.randn(4096)).astype(np.complex64)
# NVIDIA via cuFFT
X = gpufft.fft.fft_1d_c2c_pow2(x, log_n=12, backend="cuda")
# Same call on any Vulkan GPU via VkFFT
X = gpufft.fft.fft_1d_c2c_pow2(x, log_n=12, backend="vulkan")
# Arbitrary (non-power-of-two) sizes
y = (np.random.randn(1000) + 1j * np.random.randn(1000)).astype(np.complex64)
Y = gpufft.fft.fft_1d_c2c(y, n=1000, backend="cuda")
The fft_1d_c2c_pow2 signature matches
ferrum-gpu's, so code written against
one package runs on the other. ferrum-gpu is the pure-Rust kernel path
(transparent, hackable); gpufft is the vendor-library path (near-parity
performance, cross-vendor today).
Persistent device handles
dev = gpufft.cuda.Device(0) # or gpufft.vulkan.Device(0)
X = gpufft.fft.fft_1d_c2c_pow2(x, log_n=12, device=dev)
Runtime requirements
- NVIDIA path: an NVIDIA driver providing
libcufft.so(CUDA 13.x). - Vulkan path: a Vulkan 1.x loader (
libvulkan.so.1) and an installed ICD.
Neither library is bundled; both are loaded from the system at runtime.
Status
This release ships 1D complex-to-complex transforms on both backends.
2D/3D, real transforms (R2C/C2R), and f64 are on the roadmap.
Apache-2.0.
Metadata
Release files for gpufft 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gpufft-0.1.4-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details |
Release files / gpufft-0.1.4-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | gpufft-0.1.4-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7040af249391e8ec2db0fdc543403c8eeed0286eea008b5c140cfb91c9bd72f2
|
|
BLAKE2b-256 checksum How to use checksums |
3fb7f2a670532fd1aee93b2eac2a118f11eb4532adaa2ce36642686747480f79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for gpufft 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for gpufft-0.1.4-cp310-abi3-manylinux_2_28_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.