PolishFX 1.0 - First Godot 4 Sprite Juice Stack Test for Indies 2026

If you are searching polishfx godot after the August 12, 2026 1.0 launch, the useful question is not whether stackable sprite juice looks cool in a browser demo - it does. The useful question is a pipeline decision: will one shared ShaderMaterial with outline + glow + hit flash actually survive a room full of enemies without every sprite flashing together, will it stay at playable FPS on Mobile/Compatibility, and is Lite (free, MIT, 8 effects) enough for your first pass - or do you need Full (28 effects, 14 presets, gallery) tonight?

PolishFX is one uber-shader for Godot 4.4+: check boxes and sliders on a single material, drive one-liners like PolishFX.flash($Enemy) from GDScript, and keep per-node live params so hundreds of sprites can share one material without the "every enemy flashes at once" bug. The 1.0 launch post and product page are the authoritative feature sources. An announcement is a ceiling. This tutorial is a floor test on one scene.

This article turns the launch into a 60-120 minute P1-P6 keep/hold lab. You will install Lite first into a disposable 2D scene, stack three effects on one sprite, prove per-node flash isolation on two enemies sharing one material, check FPS under a stress count, try one UV-space effect against a spritesheet honesty gate, decide Lite vs Full with a CapEx four-liner, and write polishfx_1_0_juice_receipt_v1.json. You will not juice your whole cast tonight.

Non-repetition: this is not 12 free VFX texture and flipbook sources, which is a texture/flipbook listicle. It is not the 5-day shader challenge, a general daily VFX practice. This URL owns one intent: is PolishFX 1.0 worth adopting for your Godot 4 sprite juice, tested Lite-first with honest Full and performance hold criteria?

Time estimate: 60-120 minutes on a disposable Godot 4.4+ 2D scene. Add 20 minutes only if you also want a store-capsule screenshot pass.

Default recommendation: keep Lite for new 2D juice experiments if P1-P4 pass - it is free MIT and proves the shared-material model. Buy Full only after P5 shows you need more than eight effects or the presets/gallery, and after P4 proves FPS under your real enemy count. Hold pasting PolishFX onto every spritesheet-heavy atlas until you read the UV-effect limitations and verify one problem frame.

What PolishFX 1.0 actually ships

Strip the launch marketing and keep the operator facts.

• One uber-shader, 28 stackable effects on a single ShaderMaterial - outline + glow + freeze + flicker at once, no shader-merging archaeology.
• Per-node live params via canvas instance uniforms (Godot 4.4+) so many enemies share one material and still flash/dissolve individually.
• One-line API, no autoload required: PolishFX.flash($Enemy), PolishFX.squash($Player), await PolishFX.dissolve_out($Boss).finished, PolishFX.preset($Statue, "golden").
• Zero art files - pure shader + GDScript; works on Sprite2D, AnimatedSprite2D, TextureRect, and similar.
• 14 presets on Full: frozen, poisoned, cursed, hologram, ghost, golden, retro, neon, stone, toxic, glitched, jelly, shadowed, rainbow_toy.
• Every renderer: Forward+, Mobile, Compatibility (the itch demo is the pack in browser). Author stress claim: ~200 juiced sprites on one material at 65–144 FPS.
• Lite vs Full: Lite = 8 effects, MIT, free; Full = 28 effects + presets + interactive gallery, commercial license, launch sale about $9.89 (34% off $14.99 - verify at checkout).
• Honest limit: some UV-space effects (shine sweep, bulge, rainbow spread, UV scroll, pixelate at frame borders) want one texture per frame rather than packed spritesheets - details in the README.

The 28 effects by stage (operator map)

Lite includes eight of these - enough to prove stack + API + shared-material behavior before you pay. Treat Lite as the test harness, not a permanent ceiling if your game needs status looks (poisoned, frozen) and dissolve deaths.

Monday ritual - Lite first, six gates, one buy/hold

If you only have 60 minutes, stop after P2. Shared-material isolation is the feature that separates PolishFX from "duplicate material per enemy" juice hacks.

Company CapEx four-liner

1. Scope - evaluate Lite (free) on a disposable scene tonight; Full purchase only if P5 proves need.
2. Cost - Lite is $0 / MIT. Full launch sale about $9.89 (list $14.99) - verify tax and sale end date on itch. No subscription.
3. Trap - shipping Full under the wrong license assumption, or assuming every UV effect works on packed spritesheets without the README limitations pass.
4. Owner - one named artist/TA owns the stack style guide, FPS budget, Lite→Full purchase gate, and capsule screenshot honesty.

Prerequisites

• [ ] Godot 4.4 or newer (canvas instance uniforms for per-node params).
• [ ] A disposable 2D project or scene with at least two Sprite2D / AnimatedSprite2D nodes.
• [ ] Download PolishFX Lite first from the itch page (MIT).
• [ ] Optional: a spritesheet atlas you already use, to stress the UV-effect honesty gate.
• [ ] Read the 1.0 launch post so you know today's Lite/Full split.

Beginner glossary

• Juice: feedback that makes actions feel responsive - flashes, squash, shake, dissolves.
• Stackable shader: multiple effects on one material at once, toggled independently.
• Per-node live params: instance-level values so shared materials can animate differently per sprite.
• Hit flash: brief bright flash when damage lands.
• Dissolve: alpha burn-away death/transition, often awaitable.
• Spritesheet / atlas: many frames packed into one texture - some UV effects misbehave at frame borders.

P1-P6 - the one-evening stack test

P1 - Three-effect stack that reads at play scale

Copy the Lite folder into the project. Assign the PolishFX material to one hero sprite. Enable three Lite effects that matter for readability - for example outline + glow + hit flash, or outline + squash + flicker. Tune sliders until the look reads at your intended camera distance.

Check: does the stack read on a dark and a light background? Does it survive a 50% UI scale preview (capsule honesty)?

Pass P1 when one sprite has a deliberate stacked look you would ship, not three effects cranked to maximum.

Stack style guide (copy into the art bible):

If two roles share a look, players stop reading threat. PolishFX makes stacking easy - that is why a style guide is mandatory, not optional.

P2 - Shared material, isolated flash (the decisive gate)

Duplicate the enemy (or place two). Assign the same PolishFX material instance policy the docs recommend for shared materials. Call flash (or toggle the flash param) on enemy A only.

Check: does enemy B stay calm? If both flash, you duplicated materials the old way or missed instance uniforms - fix before buying Full.

Pass P2 when only the targeted node reacts. This is the backlink magnet: a shared-material juice contract other Godot 2D teams can cite.

P3 - One-line API without autoload theater

From a short script (player hurt, timer, or input):

PolishFX.flash($Enemy)
PolishFX.squash($Player)
# Full-only example - skip on Lite:
# await PolishFX.dissolve_out($Boss).finished

Check: does the call work from gameplay code without a global singleton ritual? Is the API discoverable enough that a teammate can copy the pattern?

Pass P3 when one gameplay-triggered call works and the code is short enough to paste into Discord.

P4 - Performance hold under a real count

Instance 50 juiced sprites sharing one material, then climb toward your real max room count (or the author's ~200 claim if you have headroom). Note FPS on Forward+ and, if you ship mobile/web, on Mobile or Compatibility.

Check: does FPS stay above your floor (for many indies: 60 desktop / 30 mobile)? Does enabling extra effects (glow + outline + flash) drop you under budget?

Pass P4 when your stress count is documented with a pass/fail FPS. If you only pass at tiny counts, hold Full until you simplify stacks or cull offscreen juice.

P5 - UV / spritesheet honesty + Lite vs Full

If you use packed spritesheets, enable one UV-space effect (pixelate, wave, glitch, bulge, UV scroll, shine sweep - whichever Lite includes or Full unlocks). Inspect frame borders.

Check: do you see edge artifacts? If yes, document "one texture per frame required" for that effect, or use a workaround from the README - do not discover this after a capsule shoot.

Then decide Lite vs Full:

Pass P5 when the spritesheet note and Lite/Full decision are written - not when you "feel" you need more effects.

P6 - Capsule/screenshot honesty + share note

Capture a before/after at store-capsule scale. Juice that only looks good zoomed in is a hold for marketing screenshots. For pixel readability discipline, pair with 10 pixel art composition rules and combat timing notes from pixel art combat FX.

Share note:

PolishFX 1.0 evening (YYYY-MM-DD)
Godot: [4.4+]  Edition: Lite / Full  Renderer: [Forward+/Mobile/Compat]
P1 three-effect stack: pass/fail
P2 shared-material isolated flash: pass/fail
P3 one-line API: pass/fail
P4 stress count [N] @ [FPS]: pass/fail
P5 spritesheet/UV note: [ok / limited]
Decision: keep Lite / buy Full / hold

Pass P6 when the note and receipt exist with a named owner.

Lite vs Full - buy criteria (print this)

Do not buy Full to "fix" a failed P2. Shared-material isolation is a setup issue, not a SKU issue.

Who should hold

• Projects on Godot older than 4.4 - upgrade first or you lose the per-node live-param story.
• Atlas-heavy games that depend on UV-space looks - finish the honesty gate before a style lock.
• Teams without an FPS budget - juice without a floor becomes a ship blocker on Mobile/Compatibility.
• Anyone stacking five effects on every sprite "because they can" - readability and cost both suffer; style-guide the stacks.

PolishFX pairs with spawn-style kits (the author points at KapowFX for impacts/explosions). Keep roles clear: PolishFX lives on sprites; spawn VFX kits cover moments. For free texture/flipbook libraries when you still need art files, see 12 free VFX texture and flipbook sources. Broader shader tooling sits in 25 free tech-art tools and shader-graph libraries.

Common mistakes

• Starting on Full. Lite proves the architecture for free.
• Duplicating materials per enemy. That reintroduces the flash-everything bug PolishFX exists to avoid.
• Cranking every slider. Three readable effects beat eight noisy ones.
• Ignoring spritesheet UV limits. Frame-border artifacts show up late in capsuling.
• Skipping Mobile/Compatibility. The browser demo proves Compatibility can work - your content density might not.
• Mixing PolishFX with custom canvas shaders carelessly. Know which material wins on the sprite.

Troubleshooting order

1. Nothing visible - is Godot 4.4+? Is the material actually assigned? Is the effect enabled?
2. Every enemy flashes - shared material / instance uniform setup; re-do P2.
3. API call does nothing - node path wrong, or calling Full-only APIs on Lite.
4. FPS dies - reduce stack complexity, cull offscreen, lower stress count; re-run P4.
5. UV artifacts on atlas - switch to per-frame textures for that effect, or drop the UV effect.
6. Script errors after copy - isolate GDScript issues with common Godot GDScript fixes; confirm the folder landed where the README expects.
7. Particles/layers confusion - if GPUParticles2D vanish while juicing UI layers, separate that bug with GPUParticles2D canvas-layer visibility.

What teams should do next Monday

Solo 2D indie

• Install Lite, finish P1-P2, ship one juiced enemy in a prototype build.
• Buy Full only after a written P5 need.

Small art + code pair

• Artist owns stack style guide (max effects per role: player / enemy / pickup).
• Engineer owns shared-material setup and FPS budget in CI smoke if you have one.

Company / outsourcer

• License table in the art bible (MIT Lite vs Full commercial).
• Require the juice receipt before style lock for a milestone.

Creator / educator

• Post a 10-second before/after of isolated flash on shared materials - that teaches the architecture better than a feature list. For daily practice energy, the 5-day shader challenge still works as a warm-up without replacing this PolishFX-specific keep/hold.

Key takeaways

1. PolishFX 1.0 (Aug 12, 2026) is a stackable Godot 4.4+ sprite-juice uber-shader (launch post).
2. Lite is free MIT with 8 effects; Full adds 28 effects, 14 presets, and a gallery (product page).
3. Per-node live params let many sprites share one material without synchronized flashes.
4. One-line API (flash, squash, awaitable dissolve on Full) needs no autoload.
5. Works on Forward+, Mobile, Compatibility - still verify your stress count.
6. Some UV-space effects want one texture per frame, not packed spritesheets.
7. Test Lite first; do not buy Full to fix a failed shared-material setup.
8. P2 isolated flash is the decisive architecture gate.
9. P4 FPS under a real enemy count is the performance hold.
10. Style-guide stacks - three readable effects beat eight noisy ones.
11. Keep PolishFX for on-sprite juice; use spawn VFX kits for impacts/explosions.
12. A before/after + receipt is the cite-worthy artifact, not a changelog reaction.

FAQ - PolishFX 1.0

What is PolishFX for Godot?

PolishFX is a single stackable ShaderMaterial plus GDScript helpers that add sprite juice (flash, outline, glow, dissolve, and more) without opening an image editor. Version 1.0 targets Godot 4.4+.

Is there a free version of PolishFX?

Yes. Lite is free under MIT with eight stackable effects and the one-line API / per-node live params. Full is the paid commercial pack with all 28 effects, 14 presets, and an interactive gallery.

Does PolishFX require Godot 4.4?

Yes for the full per-node live-param story (canvas instance uniforms). Confirm your project version before adopting.

Will every enemy flash if they share one material?

Not if you set up per-node live params correctly. That shared-material isolation is a primary reason to evaluate PolishFX - verify it with the P2 gate before buying Full.

How much does PolishFX Full cost?

On the 1.0 launch page, Full was about $9.89 during a 34% launch sale off $14.99. Verify current pricing and sale end date on itch before purchasing.

Do UV effects work on spritesheets?

Some UV-space effects want one texture per frame rather than packed atlases, especially near frame borders. Test your atlas in P5 and read the README limitations before a style lock.

Can PolishFX replace a VFX spawn kit?

No. PolishFX lives on sprites (states, statuses, deaths, selection). Spawn kits cover moments (explosions, hitstop, popups). Many 2D games want both roles.

Should I buy Full on day one?

Only if P1-P4 already passed on Lite and you have a concrete need for more effects or presets. Otherwise keep Lite and revisit after a real combat pass.

Related reading

• 12 Free Godot 2D Juice and VFX Tools After PolishFX Lite - 2026 — what else to install around Lite, with a channel-conflict table
• 5-Night Godot Juice Challenge - PolishFX Lite Before You Buy Full 2026 — turn this evaluation into a five-night practice with a buy/hold decision
• 12 Free VFX Texture and Flipbook Sources - Stylized Combat 2026
• 5-Day Shader Challenge - One Visual Effect Per Day
• 10 Pixel Art Composition Rules - Readability In-Game 2026
• Pixel Art Combat FX - Hitstop, Smear Frames, Impact Timing
• 25 Free Tech-Art Tools and Shader-Graph Libraries
• 30 Free 2D Game Art Assets - Sprites Curated List
• GDScript Syntax Errors - Common Godot Fixes