FXBlurView: A Deprecated iOS Blur Library That Still Teaches Real-Time Rendering Trade-Offs
GitHub describes it as [DEPRECATED]. The repository metadata lists Objective-C as its primary language. The metadata lists the NOASSERTION license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- FXBlurView replicates the iOS 7 realtime background blur on iOS 5 and above, but it is deprecated. This review covers its two modes, performance pitfalls, and why you should probably migrate.
- Who is it for?
- FXBlurView is for legacy projects that must support iOS 5 or 6 and need a simple blur effect without modern dependencies. Do not adopt it for new development, as it is deprecated and untested beyond iOS 8.4.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- No. The owners have archived the repository on GitHub, so it is read-only and no longer receives changes.
- What is it written in?
- Mainly Objective-C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- nicklockwood/FXBlurView4,908 ★ · -18
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| nicklockwood/FXBlurView | 4.9k | 4.9k |
-18 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What FXBlurView Solves and Who It Was For
FXBlurView solves a specific problem: bringing the iOS 7 realtime background blur effect to older iOS versions. The README states that it works on iOS 5 and above, with compatibility down to iOS 4.3. The target audience is developers who needed a frosted-glass look for navigation bars, menus, or overlays without requiring users to upgrade to iOS 7. The library is a UIView subclass, so it integrates directly into existing view hierarchies. It also extends UIImage with a method to blur images statically. This is not a general-purpose UI framework; it is a single-purpose component for one visual effect. The project is now deprecated, which means the problem it solved has been largely superseded by Apple's own UIVisualEffectView, introduced in iOS 8. For anyone starting a new project today, this library is the wrong starting point. For historians or maintainers of old code, it shows how developers worked around system limitations before Apple provided a native solution.
How the Blur Mechanism Works: Static and Dynamic Modes
The core mechanism is a UIView subclass that captures the content behind it, applies a blur using the Accelerate framework, and displays the result. The README describes two modes. Static mode renders the blur once when the view is added to a superview. You can force a redraw by calling setNeedsDisplay or updateAsynchronously:completion:. Dynamic mode automatically redraws on a background thread as often as possible. The documentation warns that dynamic blurring is extremely CPU-intensive. The updateInterval property controls the frequency of updates; a value of zero means as fast as possible. The iterations property controls quality; more iterations mean better quality but lower performance. The blurRadius defaults to 40 points, similar to iOS 7. There is also a tintColor property, but its alpha component is ignored, which is a subtle limitation. The UIImage extension provides a one-shot blur method, which is useful for static images. The dynamic mode's background thread redraw is a key design choice to keep the main thread responsive, but it still taxes the CPU heavily.
Installation and Configuration: Real Commands and Properties
Installation is manual: drag the class files into your project and add the Accelerate framework. You can create FXBlurView instances programmatically or in Interface Builder by changing a UIView's class. For custom properties, the README suggests using User Defined Runtime Attributes or an IBOutlet. The key configuration properties are blurEnabled, dynamic, iterations, updateInterval, blurRadius, and tintColor. The global methods setBlurEnabled: and setUpdatesEnabled/Disabled allow toggling blur or updates across all instances. For example, you can disable updates before an animation to avoid stuttering, but the calls must be balanced. The README gives a specific command for non-ARC projects: add the -fobjc-arc compiler flag to FXBlurView.m. This is a concrete step.
Performance Costs and Failure Modes
The documentation is explicit about performance: dynamic mode is extremely CPU-intensive. The updateInterval property defaults to zero, which means the view updates as fast as possible, potentially degrading the rest of the app's performance, especially on older devices. The README advises increasing updateInterval to alleviate this. Another failure mode is the alpha component of tintColor being ignored, which can surprise developers expecting alpha to control tint intensity. The README also notes that blurring can cause animation stutter, so you must disable updates before animations. If you forget to re-enable updates, the calls are unbalanced and updates stay disabled. The project is deprecated, meaning no bug fixes. Since it targets iOS 8.4 at most, it may not compile with modern Xcode versions without modifications. The licence field reads NOASSERTION, but a LICENCE.md file sits at the repository root, so read it for the terms. These are genuine limitations, not hypotheticals.
Comparison with Apple's UIVisualEffectView
The obvious alternative is UIVisualEffectView, Apple's native blur view introduced in iOS 8. The difference in approach is significant. UIVisualEffectView uses a system-managed blur and vibrancy effect that is optimized and hardware-accelerated; it requires no manual blur radius or iterations. FXBlurView, in contrast, performs software blurring using Accelerate, which gives developers control over radius and iterations but at the cost of CPU usage. UIVisualEffectView also supports dynamic changes automatically without a background thread, and it respects the system's appearance. However, UIVisualEffectView is only available on iOS 8 and later, so FXBlurView targeted iOS 5-7. For modern projects, UIVisualEffectView is the clear choice. The key trade-off is control versus performance: FXBlurView offers granular control but requires manual management, while UIVisualEffectView is a black box that just works.
Maintenance, License, and Upgrade Path
The maintenance cost is high because the project is deprecated. The README warns it will not receive updates or bug fixes. The last supported build target is iOS 8.4 with Xcode 6.4, which is ancient. Any modern Xcode may require changes to compile, such as updating for newer SDKs or ARC settings. The license field is listed as NOASSERTION, but a LICENCE.md file sits at the repository root, so read that file for the terms. The upgrade path is to migrate to UIVisualEffectView if your deployment target is iOS 8 or later, or to another maintained solution. The README explicitly says, 'please migrate to another solution.' That is the strongest signal that you should not invest in this library.
Editorial conclusion
FXBlurView is for legacy projects that must support iOS 5 or 6 and need a simple blur effect without modern dependencies. Do not adopt it for new development, as it is deprecated and untested beyond iOS 8.4. If you must use it, verify it compiles with your current Xcode and iOS deployment target, and test on actual devices because dynamic mode is CPU-intensive. For production, use UIVisualEffectView on iOS 8+ or another maintained solution. The concrete judgement: FXBlurView is a historical artifact, not a viable choice for new projects.
Frequently asked questions
Is FXBlurView still maintained?
No. The repository is archived, the README opens with a warning that the project is deprecated and will receive no future updates or bug fixes, and the last push was on 2020-11-18. It asks anyone using it to migrate to another solution.
What is the difference between static and dynamic mode in FXBlurView?
Static mode renders the blur once when the view is added to a superview, and you can force an update with setNeedsDisplay or updateAsynchronously:completion:. Dynamic mode, which is the default, redraws automatically on a background thread as often as possible, which the README calls extremely CPU intensive.
How do I use FXBlurView in a project that does not use ARC?
Add the -fobjc-arc compiler flag to FXBlurView.m through Build Phases, Compile Sources in your target settings. The other route is to comment out the #error line in FXBlurView.m and run Edit > Refactor > Convert to Objective-C ARC in Xcode with the files you want converted checked.
What are the default blur settings in FXBlurView?
blurRadius defaults to 40 points, which the README compares to the iOS 7 blur effect, and iterations defaults to 2, where more iterations means better quality and less performance. updateInterval defaults to zero, meaning the view updates as fast as possible.
Does the FXBlurView tint colour support transparency?
No. The README states that the alpha component of tintColor is ignored, both on the view property and in the UIImage extension, so the intensity of the tint is varied with brighter or darker colours. Set the value to nil or to [UIColor clearColor] to remove the tint.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/nicklockwood-fxblurview)Star history chart for your README
[](https://hysenlabs.com/projects/nicklockwood-fxblurview)Was this useful?