// Tech

@react-three/postprocessing — Effects for R3F

The R3F-native bindings for the postprocessing package — bloom, FXAA, vignette, depth-of-field, all as React components.

Get a quote All 3D services

@react-three/postprocessing wraps the postprocessing npm package in React components. Same effects (bloom, FXAA, vignette, depth-of-field, chromatic aberration), declarative API. You wrap your scene in <EffectComposer> and add <Bloom intensity={1.5} /> or whatever effects you need. The composition is React-native — effects can be conditionally rendered based on device tier, props can be controlled by leva sliders, GSAP can animate effect parameters. On low-tier mobile I disable all effects via `<EffectComposer disabled={isLowTier}>`. For premium desktop I usually run bloom + FXAA + vignette as the standard stack.

What you get hands-off

After delivery: the complete source handed over, commented code, and the asset pipeline documented. Hosting, SSL, nightly backups and maintenance can be part of the written offer if you need them.

// Need it on a live site? Three.js website development: 3D heroes, product viewers and scroll scenes from your models

What this delivers

Concrete output: a working r3f postprocessing integration on a real production site, not a demo. The integration includes device-tier detection so weak phones get a lighter version automatically. Source files are handed over in their original formats — Blender, GLSL, glTF — so any future developer can continue where I stopped.

How I work with it

On a typical project, r3f postprocessing ships as a self-contained module: one entry-point JS file, one CSS file, asset bundle below 1.5MB total. I keep the integration sandboxed so the rest of the site stays SEO-friendly classical HTML. Frame budget targets 60 FPS on a mid-range Android, with a measurable fallback below.

Performance budget

Lighthouse mobile target: 85+ across all categories. Before launch I run a mobile Lighthouse test and send you the result. Asset compression: glTF + Draco for meshes, KTX2 for textures, Brotli for shaders. Lazy-load any r3f postprocessing scene that isn't above the fold, with a first-paint target under 1.5s.

Frequently asked questions

Why pick this technology over alternatives?
It has the largest production-quality ecosystem, the most documentation, and the largest pool of developers who know it. For a site you want to maintain for 3+ years, ecosystem maturity matters more than feature peak.
What if a newer tool comes out next year?
I track new tooling and migrate when it makes sense, but only after the new tool ships stable production releases for at least 6-9 months. I don't rebuild client sites on bleeding-edge tools — that's the path to broken sites.
How long does this take?
It depends on scope. A simple site usually takes 1–2 weeks, larger projects take longer, and the exact timeline is in the written offer.
What does it cost?
Every project is quoted per scope — scene count, asset complexity and interactivity drive the effort. Send a short brief and you get a written fixed quote, with source code included.
What if my visitors are on weak phones?
The site detects device tier before the first scene loads and serves a lighter version on weak hardware (fewer particles, simpler shaders). Devices without WebGL get a static fallback that preserves the visual language and conversion path.

Ready to ship a 3D experience?

Tell me what you need — clear written scope, no surprises.

Get a quote +381 61 224 8989
Call
// Legal

Privacy Policy

Last updated: 2 November 2026.

This document explains, in plain language, what data I collect, why I collect it and how I keep it. No fine print.

Data controller

The data controller is D. Svilenković. I run this site, so for any question about your data email dimitrije@svilenkovic.com or call +381 61 224 8989.

What data I collect

  • When you write through the contact form: name, email, phone, project type and description.
  • When you use the free website check: the site address, the email for the report and your name if you enter it. The report goes only to that address.
  • When you visit the site: basic visit info (which page, time on page, device and browser).
  • When you become a client: details needed for invoicing (company name, tax ID, address).

Why I collect it

  • To reply to your inquiry and offer a solution.
  • To deliver the work and issue an invoice.
  • To see which parts of the site are useful and improve them.

Legal basis: your consent for visit statistics, steps taken at your request before entering into a contract for replying to an inquiry, and a legal obligation for invoices.

Who I share data with

I don't sell your data or share it with third parties for marketing. I use Google Analytics for visit statistics, only if you accept it in the cookie banner, and the site is hosted on a netcup GmbH server in Germany (EU).

The form is protected by a check that runs in your browser and on this server, without third-party services: a short background calculation, a time token and a limit on the number of inquiries. Your IP address is not stored for this check, only a one-way record of it that changes every day.

How long I keep it

Contact-form inquiries are kept up to 24 months, the typical span of pre-sale communication. Invoice data is kept as long as the law requires (up to 10 years).

Website check requests are kept just as long as inquiries, up to 24 months. The technical result of the check, without your email, is deleted after 30 days.

Your rights

At any time you can ask what data I hold, request correction or deletion, or withdraw consent. Email dimitrije@svilenkovic.com and I'll reply promptly.

Cookies

Essential cookies remember your language and your cookie choice for up to 12 months. Google Analytics 4 (Google Ireland Ltd) loads only after you click “Accept all” and sets cookies starting with _ga for up to 14 months. Advertising features and Google signals are off, and statistics are kept for 14 months. Data may be transferred to Google LLC in the USA under the EU-US Data Privacy Framework. When you withdraw consent, these cookies are deleted.

Complaints

If you think something isn't right, write to me first and I'll sort it out quickly. You also have the right to complain to the Commissioner for Information of Public Importance and Personal Data Protection.

Changes

If something changes, I'll update this page and the date at the top.
// Legal

Terms of Service

Last updated: 1 November 2026.

These terms describe how we work together. They're written in plain language — if anything is unclear, just ask.

Who provides the service

The service is provided by me, D. Svilenković, and I build the sites and apps myself. Contact: dimitrije@svilenkovic.com, +381 61 224 8989.

What I do

I build websites, web and desktop apps, online stores, Excel automation, appointment booking, system integrations, hosting and maintenance. I also make videos for social media, run Instagram, Facebook, TikTok and LinkedIn profiles, write posts and create AI images for them.

How we agree on work

  1. You tell me what you need. The conversation is non-binding.
  2. I send you a quote with the price and the timeline.
  3. When you confirm the quote, I start development.

Price and payment

The price is fixed and agreed upfront. You get the payment terms and the timeline in the quote before work starts. If the scope changes significantly, we agree on the new price before continuing.

Timelines

I give a deadline in the quote and stick to it. If I need material from you (images, text, access), please send it on time, because the deadline depends on it.

Revisions

Small revisions are included and done at no charge. Larger changes that go beyond the original scope are agreed separately.

Ownership

Once paid, everything I built is yours. You can use it, change it or move it to another developer without involving me.

Hosting and maintenance

I can host the site on my server and maintain it after it is built, and the quote states what that covers. You can move the site to another host at any time.

Liability

I do my best to make everything work as it should, but bugs happen. As soon as you report one, I fix it as fast as possible. My liability is limited to the amount paid for the project.

Cancellation

You can cancel at any time. You pay only for the work done up to that point, and receive all the materials and code you've paid for.

Disputes

If a disagreement arises, we'll first try to resolve it by talking. If that fails, the law of the Republic of Serbia applies and the court at the provider's seat is competent.

Changes to these terms

These terms may be updated. The last-updated date is shown at the top — you can always see what currently applies.