fspy.io

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

Yes. fSpy is open source software and is totally free to download and use. The site also offers an optional donate button for anyone who wants to support the project, with the amount left entirely up to the user. Donations are accepted through PayPal.

What "Free" Covers

The download is available for Mac, Windows, and Linux, and there is no paid tier described on the site. The software is described as open source, cross platform, and built for still image camera matching.

If You Want to Support fSpy

Donating is presented as a choice rather than a requirement. The site's own framing is that you can pay whatever amount makes sense to you — including nothing, since the software remains free either way. If you do decide to contribute, the donate button on the site routes through PayPal.

What fSpy Actually Does

fSpy is a still image camera matching tool. You use it to work out the camera parameters behind a photograph, then carry those parameters into a 3D application so a rendered camera lines up with the original image.

Two paths are documented on the site:

• Blender — an official fSpy importer add-on sets the Blender camera parameters and can optionally set the camera background image.
• Other applications — without a dedicated importer, you copy the fSpy parameter values one by one into the target application.

Getting Parameters Into Apps Without a Dedicated Importer

The site outlines this process:

1. Set the camera viewport to match the dimensions of the input image.
2. Use the input image as the camera background.
3. Set the camera field of view.
4. Set the camera position.
5. Set the camera orientation.
6. Set the principal point, unless it coincides with the image midpoint.

Bottom Line

There is no cost barrier to using fSpy, and no account or payment is needed to download it. Donating is purely optional and handled through PayPal if you choose to do it.

fSpy only ships an official importer for Blender. For any other 3D application, you transfer the solve manually: copy each camera parameter out of fSpy and paste it into the matching field in the target app. This works in any program that lets you set a camera's field of view, position, orientation, and principal point, but it is a per-value process with no automation, so expect to do it by hand every time.

What you are actually transferring

fSpy solves the camera that took a still image. The output is a small set of numbers describing that camera, and those numbers are what you reproduce in the target application:

• Field of view (derived from the focal length and sensor size)
• Camera position in 3D space
• Camera orientation (rotation)
• Principal point, unless it coincides with the image midpoint

If the target app has no concept of one of these, you cannot fully match the shot — for example, a program that only exposes a focal length slider but no principal point offset will be close but not exact.

Step-by-step manual transfer

The official fSpy guidance for applications without a dedicated importer outlines this sequence:

1. Match the viewport to the image. Set the camera viewport (render resolution or camera frame) to the same dimensions as the input image. If the aspect ratios differ, the field of view you paste in will frame the scene incorrectly.
2. Set the input image as the camera background. This gives you a visual reference to align against while you enter the remaining values.
3. Set the camera field of view. Enter the fSpy field of view (or the equivalent focal length plus sensor size, if that is how the target app expresses it).
4. Set the camera position. Copy the position values from fSpy into the target camera's location fields.
5. Set the camera orientation. Copy the rotation values. Watch the axis convention — many apps use a different up-axis or rotation order than fSpy, so you may need to convert.
6. Set the principal point, unless it coincides with the image midpoint. If fSpy reports a principal point at the center, you can skip this step.

Verifying the result

After entering the values, the background image should line up with the 3D scene the way it did in fSpy. A quick check: place a simple object at a known point in the image (a corner of a building, a table edge) and confirm it sits where the photo shows it. If everything is shifted or scaled, the usual culprits are a viewport size that does not match the image, or a rotation/axis mismatch.

Common snags

• Aspect ratio mismatch — the single most common cause of a wrong-looking solve. Fix the viewport dimensions first.
• Axis and rotation order differences — position and orientation values are not always portable between apps without conversion.
• No principal point control — some apps do not expose it, so off-center shots cannot be matched exactly.
• Unit scale — if the target scene uses different units, position values may need scaling.

When manual transfer is not worth it

If you are working in Blender, skip all of this: there is an official fSpy importer add-on that sets the Blender camera parameters and can optionally set the camera background image for you. Manual transfer is the fallback for everything else.

fSpy itself is open source and free to download and use on Mac, Windows, and Linux, with an optional donation.

Blender has an official fSpy importer add-on, so you don't have to copy camera values by hand. Install and enable the add-on, run fSpy on your still image, save the .fspy project, then use the add-on's import operator in Blender to set the camera parameters — and optionally the camera background image — in one step. This works for any Blender user who needs to match a 3D camera to a photo; if you use a different 3D application, you'll fall back to the manual copy-and-paste route described below.

What you need first

• fSpy installed and running. It's open source, cross-platform (Mac, Windows, Linux), and free to download and use.
• A still image with enough straight-line features (edges, rectangular shapes, architectural lines) for fSpy to solve the camera.
• Blender installed, with permission to install add-ons.

Step 1: Solve the camera in fSpy

1. Open your image in fSpy.
2. Set the image dimensions and place the vanishing-point guides along lines in the photo until the calibration is consistent.
3. Confirm the estimated focal length and principal point look reasonable.
4. Save the project as an .fspy file. This file carries the camera parameters the Blender add-on reads.

The quality of the match depends on this step. If the guides are sloppy, the imported Blender camera will be wrong no matter how clean the import is.

Step 2: Install the official fSpy importer add-on

The fSpy site points Blender users to an official importer add-on and its instructions. Install it the normal Blender way:

1. Download the add-on.
2. In Blender, open Edit > Preferences > Add-ons.
3. Use Install… and select the add-on file.
4. Enable the checkbox next to the add-on so it loads.

The add-on is what sets the Blender camera parameters from the .fspy data, and it can optionally set the camera background image.

Step 3: Import the .fspy file

1. In Blender, select or create the camera object you want to drive.
2. Run the fSpy import operator provided by the add-on.
3. Choose the .fspy file you saved.
4. Decide whether to also set the camera background image. Enabling it loads your reference photo behind the camera so you can line up geometry against it.

Expected result: the Blender camera's field of view, position, orientation, and principal point are set to match the photo, and — if you enabled it — the image appears as the camera background.

Step 4: Verify the match

• Look through the camera (numpad 0 by default) and check that the background image lines up with the scene.
• If you placed geometry using the photo as reference, confirm edges that should be parallel in the real scene converge correctly.
• If the framing is off, the usual cause is a bad fSpy solve, not the import. Re-check the vanishing-point guides and re-export.

If you're not using Blender

For applications without a dedicated importer, fSpy's own outline is to copy the parameter values one by one into the target application. The process:

1. Set the camera viewport to match the dimensions of the input image.
2. Use the input image as the camera background.
3. Set the camera field of view.
4. Set the camera position.
5. Set the camera orientation.
6. Set the principal point, unless it coincides with the image midpoint.

This is more error-prone than the Blender add-on because every value is transferred manually, but it works in any application that exposes those camera controls.

Common snags

• Add-on not visible after install: make sure it's enabled in Preferences, not just installed.
• Camera looks right but background is missing: the background image is optional; re-run the import with that option enabled.
• Everything is skewed: almost always a calibration problem in fSpy. Re-solve before touching Blender.
• Principal point ignored: in manual (non-Blender) workflows, the principal point only needs setting when it differs from the image midpoint.

fSpy is free and open source, with an optional donate button if you want to support it — paying is not required to download or use it.

fSpy is an open source, cross-platform application for still image camera matching. It lets you recover the camera parameters used to take a photograph — field of view, camera position, orientation, and principal point — so you can recreate that same virtual camera in 3D software and composite new objects into the original image. It runs on Mac, Windows, and Linux, is developed by Stuffmatic, and is free to download and use.

What problem it solves

If you want to place a 3D object into a photo and have it look like it belongs there, your virtual camera has to match the real one. Guessing the focal length and angle by eye rarely lines up. fSpy extracts those parameters from the image itself, so the 3D camera you build matches the perspective of the photo.

Typical uses:

• Compositing a 3D model into a still photograph
• Matchmoving a single image for visual effects or architectural visualization
• Rebuilding a scene's camera setup for rendering or set extension

How the workflow fits together

1. Match in fSpy — load the still image and define the perspective (for example, by marking parallel lines or vanishing directions). fSpy computes the camera parameters.
2. Get the parameters into your 3D app — either through a dedicated importer or by copying values manually.
3. Composite — use the matched camera and the original image as a background to place your 3D content.

Importing into Blender

Blender has an official fSpy importer add-on. It sets the Blender camera parameters for you and can optionally set the camera background image. This is the smoothest path and avoids manual value entry.

Importing into other applications

For applications without a dedicated importer, you transfer the parameters by hand. The general process:

• Set the camera viewport to match the dimensions of the input image
• Use the input image as the camera background
• Set the camera field of view
• Set the camera position
• Set the camera orientation
• Set the principal point, unless it coincides with the image midpoint

Availability and cost

fSpy is open source software and free to download and use. The project also offers a donate button (via PayPal) for anyone who wants to support it — paying is optional, and you choose the amount.

When to use it

Use fSpy when you have a single still image and need a matching virtual camera. If you already have a dedicated importer for your target application (as with Blender), the process is largely automatic; otherwise, expect to copy the parameter values across manually.