An AI-driven editor for deterministic visual effects. It runs entirely in the browser using WebGPU – no installation required. You can create, compose, animate, and export professional visual effects at up to 4K/60fps.

Yes. Everything works with a watermark – preview, edit, compose, animate. You only pay when you want clean output (export without watermark or live embed without watermark). Payment is made by burning Sanki tokens.

Not to use effects. You can browse Stock, pick effects, compose scenes, and export – all without writing a single line of code. If you want to create new effects, you can write WGSL shader math directly or use Creator AI to help you.

Enpixelment requires WebGPU support. Currently available in Chrome, Edge, and recent versions of Safari. Firefox support is expected as WebGPU adoption grows.

Enpixelment is a side project of Sanki. All payments on the platform use the Sanki token. The affiliate program is funded by the Sanki marketing budget.

Write your WGSL shader math (or use Creator AI to help), test it in the built-in sandbox with the performance profiler, and publish to Stock with one click. Add tags, category, and a live preview.

Prices are set by the platform per product type (image, video, live embed) – not by individual creators. This ensures fairness and consistency. Every six months, the community votes on price adjustments.

Automatically. When someone uses your effect in an export or live embed and burns Sanki to remove the watermark, a smart contract sends your share directly to your wallet. No invoices, no delays, no intermediary.

Yes, through multiple layers. Your effect code is wrapped in 500+ lines of engine template – without the engine it can’t run. What reaches the browser is obfuscated. The watermark is baked into the render pipeline and can’t be removed client-side. The economics make reverse-engineering irrational.

Your choice. You can link a public or private GitHub repository to your creator profile – for transparency, portfolio, or proof of authorship. The effect always runs from the platform regardless.

Pre-composed scenes built using Stock effects. You can create a template, share it, and earn when someone uses it. The buyer pays for every effect in the template plus your composition work. All creators involved are paid automatically.

Sanki is the token that powers the entire Enpixelment ecosystem. All payments, burns, and affiliate rewards use Sanki. It trades against BNB and USDT.

Prices are set in USD. At the moment of payment, the equivalent in Sanki is calculated at the current exchange rate. If Sanki goes up, you pay fewer tokens. If it goes down, you pay more. The dollar value stays constant.

The platform’s fee. Instead of taking a commission, the platform burns Sanki tokens permanently – removing them from the total supply. Every transaction reduces the amount of Sanki in existence. All burns are tracked live on sanki.io.

Yes. Every payment, every burn, every split is on-chain. You can verify independently without relying on any platform dashboard. The export pipeline is open source – and its production build hash is published on-chain so you can confirm it’s the same code running in production.

Never. Payments go directly from the buyer’s wallet to your wallet via smart contract. Enpixelment has zero custody of creator funds. No liability, no trust required.

The community. Every six months, the community votes on price adjustments. The platform cannot raise prices unilaterally.

Not yet. Right now, the only payment method is Sanki tokens. We plan to add fiat payment options (card, bank transfer) in the future – when you pay in USD or EUR, the system will automatically convert to Sanki behind the scenes. Same result, just a smoother on-ramp.

Enpixelment was built as a project funded by the Sanki community. It’s not a coincidence – it’s by design. Sanki has a deflationary economic model: the total supply decreases over time as tokens are burned. Enpixelment is a key part of that model. Every export, every live embed, every transaction on the platform permanently destroys Sanki tokens. The more the platform is used, the scarcer Sanki becomes. This alignment – between platform growth and token value – is what makes the economics work for everyone: creators, users, and token holders.

Yes. Affiliate commissions are funded by the Sanki marketing budget – not by the platform itself. This won’t change even when fiat payments are available. When a user pays with a credit card, the affiliate still earns in Sanki. The marketing budget exists to grow the ecosystem, and Sanki is the ecosystem’s native currency.

Micropayments. A single effect costs fractions of a dollar. Traditional payment processors charge $0.30 + 2.9% per transaction – that fee alone would exceed the price of most effects. Blockchain transactions cost a fraction of a cent regardless of amount. This makes per-effect, per-export pricing possible. Without blockchain, the only viable model would be monthly subscriptions – which means creators get pooled revenue instead of direct, per-use payment.

The engine is proprietary. The export pipeline (including the blockchain payment gate) is open source – auditable by anyone. Production build hashes are published on-chain for verification. Closed source engine, open ledger.

MP4, WebM, GIF, and PNG. At any resolution up to 4K, at up to 60fps. Pipelined GPU readback with zero-allocation export – real video production, not canvas recording.

The second pillar of the platform. While shader effects run on the GPU (math on pixels), simulation effects run in WASM (physics on entities) – particle systems, fluid dynamics, cloth, flocking. Same timeline, same audio bridge, same export pipeline. You can run simulations locally for free or upgrade to cloud compute with Sanki.

Yes, but with caveats. WebGPU rendering at 4K is real-time on modern GPUs – the shader runs at full speed regardless of whether it’s in a browser or a native app. The bottleneck is export, not rendering. Each frame must be read back from the GPU to the CPU, then encoded into video. This readback is inherently slower in a browser than in a native app. In practice: a 10-second clip at 4K/60fps might take 30–60 seconds to export, depending on your GPU. That’s slower than After Effects with hardware encoding, but faster than most people expect from a browser.

Three main ones. First, memory: a browser tab typically gets 4GB, while native apps can use all available RAM. This limits how many layers and effects you can stack in a single scene. Second, video encoding: browsers use WebCodecs (software H.264/VP9), while native apps access hardware encoders (NVENC, AMF) which are 5–10x faster. Third, file system: everything goes through downloads and uploads – there’s no direct access to your local files. The trade-off is clear: native apps are more powerful, browser apps are zero-install, cross-platform, and always up to date.

Yes – server-side rendering. The same engine that runs in your browser can run on a cloud GPU. You’d design your scene locally, then send it to a server for final export. The server has no memory limits, uses hardware video encoders, and can render at resolutions your local machine can’t handle. This is planned but not yet built. When it arrives, it will be optional: simple exports stay local and free, heavy exports use cloud compute paid with Sanki. Cost estimated upfront, no surprises.

No framework and no engine – no React, no Three.js. It ships 5 small runtime libraries (ajv, earcut, mediabunny, opentype.js, webgpu), for triangulation, media muxing and font parsing. But it’s more than that – it’s not just about avoiding downloads. The core systems are purpose-built to work together: the reactive signal system, the render engine, the audio analysis pipeline, the animation system, the composition engine, the GPU resource manager. Each piece was designed for the others, with a scalable architecture and precise synchronization between components. This isn’t a collection of open-source parts glued together – it’s a single, coherent machine where every subsystem knows exactly how the others behave.

Effects in Enpixelment aren’t plugins – they’re first-class citizens of the architecture. Every effect, whether built-in or created by a Stock creator, has the same capabilities: it can be animated with keyframes, modulated by audio, composited with blend modes, masked by paths, and exported at any resolution. Effects and post-processors are managed by a registry system that treats them identically – they participate in the render pipeline, the caching system, the undo history, and the deterministic frame calculation. There’s no “plugin API” with limited access. A Stock effect has the exact same power as a built-in one. This is what makes composition deep – you’re not stacking workarounds, you’re composing systems that were designed to interleave.

Built-in benchmarking tools for effect creators. Measures GPU time per frame, frame rate impact, resolution scaling, and memory footprint. Helps you craft professional, high-performance effects before publishing.

It’s not a question of if, but when. The entire architecture – WebGPU rendering, deterministic pipeline, effect registry, audio modulation, export – was built with extensibility in mind. 3D is the natural next step: camera, lighting, materials, mesh import, all integrated as first-class citizens alongside existing 2D layers. Not a bolt-on, not a third-party engine embedded inside – a native 3D pipeline that shares the same composition, animation, and export infrastructure. We’re actively exploring this.

Different purpose. Enpixelment isn’t becoming a 3D modeling tool. The goal is 3D as a creative layer: import a model, light it, animate it, composite it with 2D effects, react to audio, export to video – all in the browser. Think After Effects 3D, not Blender. The same philosophy that makes 2D effects powerful here – parametric, composable, audio-reactive, deterministic – will apply to 3D. Your 3D scene is just another layer in the composition.

Share a referral link for any effect, template, or the platform itself. When someone comes through your link and makes a purchase, you earn Sanki. Your commission is funded by the Sanki marketing budget – creators and buyers are completely unaffected.

No. Creator revenue, burn amount, and buyer price are all unchanged. The affiliate commission comes from the Sanki marketing budget – it’s an investment in ecosystem growth, not a cut from existing participants.