01 · Product name
OpenRefine
Clean and reconcile a messy investigative table.
Published by OpenRefine.
In short
OpenRefine is the desktop tool for messy tables. On 19 Oct 2026 the download page said it is free software under the BSD 3-clause license, and the download button offered OpenRefine 3.10.0, dated 2026-02-26 in the version table. The GitHub SPDX field is BSD-3-Clause. The latest GitHub release that day was 3.10.1, published 2026-03-04. The copy started here printed Version 3.10.0 [TRUNK] and opened a two-row project, owasp.org and example.com. The download page's word for the tool is not repeated here.
Product pricing strategy
02
Free
The download page opened on 19 Oct 2026 says OpenRefine is free software under the BSD 3-clause license. It did not print a dollar amount, a support tier, or a seat fee. The GitHub SPDX field is BSD-3-Clause. The local server at 127.0.0.1:3333 did not ask for an account or a payment. The project created here, two public rows, did not pass through a checkout. The site has a Store link for merchandise. This listing did not open the store and does not treat merchandise as a license fee. If a hosted fork or a training course charges, that price is the other party's. Quote the download page for the license and quote 3.10.0 as the build the page offered, not as a price.
Utility and features
03
The download page at openrefine.org/download, opened on 19 Oct 2026, says OpenRefine is free software released under the BSD 3-clause license. The prominent download is OpenRefine 3.10.0 for Windows, a ZIP with embedded Java. The version table on that page lists 3.10.0 (2026-02-26) for Windows, Mac, and Linux, then 3.9.5 (2025-09-02) and 3.8.7 (2024-11-21). The GitHub repository OpenRefine/OpenRefine has SPDX BSD-3-Clause. Its latest release that morning was tag 3.10.1, published 2026-03-04T21:18:45Z. The Linux tarball this listing unpacked was the 3.10.0 file named on the download page, openrefine-linux-3.10.0.tar.gz. The server it started printed Version 3.10.0 [TRUNK] and listened on http://127.0.0.1:3333/.
- Download page says 3.10.0. On 19 Oct 2026 the download button and the version table said 3.10.0, dated 2026-02-26, under the BSD 3-clause license.
- GitHub latest is 3.10.1. The latest release tag that morning was 3.10.1, published 2026-03-04. The SPDX field is BSD-3-Clause.
- The local grid has two rows. Version 3.10.0 [TRUNK] showed owasp.org and example.com. No reconciliation was run.
The welcome screen says you create a project by importing a file, and it lists TSV, CSV, Excel, JSON, XML, and other formats. A two-row CSV was imported: owasp.org with the note public site, and example.com with the note documentation example. The grid showed those two rows in columns named domain and note, with a row count of 2. No reconciliation service was called. No cluster was run. The welcome line on the local server uses a promotional adjective this listing does not copy into the short answer. BSD 3-clause on the download page and BSD-3-Clause in the SPDX field are the same license family. The version strings are not the same: the page you download from said 3.10.0, the latest GitHub release said 3.10.1, and the binary that ran said 3.10.0 [TRUNK].
- 1
Download the build the download page names, and write both that version and the GitHub release if they differ.
- 2
Import the table you mean, and keep a note of which file produced the project.
- 3
Treat a reconciliation suggestion as a suggestion until you open the entity it names.
Caveats
04
Three version sentences were on the record the same morning. The download page offered 3.10.0, dated 2026-02-26 in its table. GitHub's latest release was 3.10.1, published 2026-03-04. The process that actually started printed Version 3.10.0 [TRUNK]. Do not average 3.10.0 and 3.10.1, and do not drop the TRUNK token from the local banner.
The grid contains two rows that this listing typed: owasp.org and example.com. It does not contain a reconciliation match, a cluster, or a Wikidata id. A later reconcile step can attach the wrong entity to a name. The welcome screen is the local app, not a hosted workspace. Java on this machine was OpenJDK 21.0.12.1. That is the runtime that launched the server. It is not a version of OpenRefine. The homepage's promotional adjective is the site's. It is not a measurement.
Screenshots
05
Potential use cases
06
- A methods note needs the build that was actually started. The download page on 19 Oct 2026 offered OpenRefine 3.10.0, dated 2026-02-26, and said the BSD 3-clause license. GitHub's latest release was 3.10.1, published 2026-03-04. The local server printed Version 3.10.0 [TRUNK]. Keep the TRUNK token. The SPDX field is BSD-3-Clause.
- The two-row project is about to be described as a reconciliation. The grid showed owasp.org and example.com in columns named domain and note, row count 2. No reconciliation service was called and no cluster was run. Say the file was a CSV this listing imported. A later suggestion from a reconciliation service is still a suggestion.
- The homepage adjective is about to enter the citation. The local welcome screen uses promotional wording this listing does not adopt. The citable sentences are the license on the download page, the version table, the GitHub release, and the grid that opened. The Store link was not opened and is not a license fee.
Hard cases
The case where the first result is easy to over-read.
3.10.0 and 3.10.1 get averaged
The download page offered 3.10.0. The latest GitHub release the same morning was 3.10.1. The process that ran said 3.10.0 [TRUNK]. There is no 3.10.05 to print. A citation names the page. If the analysis used the local server, the banner token TRUNK stays in the sentence.
Practitioners using it
Posts on X from people describing a concrete use. The quote is the post. Likes and reposts are the counts saved with it, not a live total. A label marks a creator, a maintainer, a vendor, a partner, a data partner, or an investor.
Looking for a resource to explain the sorcery behind @OpenRefine ? Emma explains it BRILLIANTLY how to reconcile ur data with OpenRefine so it's ready for export as linked #opendata in @wikidata using Scottish witch data in this short vid. Check it out! https://t.co/qVRWKp3nrp pic.twitter.com/XW8f8KBijY
Plotting strategy to bulk upload my institution author profiles. Step 1 : Use ORCID API to get ORCIDs , then reconcile to wikidata & import into Wikidata items (with affiliation & orcid) using openrefine & quick statements as per https://t.co/o7sw3cmcXB
Totally new to OpenRefine but having used 2 YouTube tutorials by @ostephens I've successfully managed to reconcile a set of author name data with Wikidata and export the matches back out. Thanks @ostephens - it's made my day!
today i'm using @OpenRefine to visualize/facet/cluster Worldcat error messages for some records from a project i work on, in an attempt to better understand the patterns and prioritize how to fix some of the issues. OpenRefine really is my favorite hammer; i just love it 🥰🔨
Questions
Is OpenRefine free?
The download page on 19 Oct 2026 said it is free software under the BSD 3-clause license. The local server did not ask for a price. The SPDX field is BSD-3-Clause.
Which version was started?
The tarball from the download page was 3.10.0. The server printed Version 3.10.0 [TRUNK]. GitHub's latest release the same day was 3.10.1, published 2026-03-04.
Citations
07
Titled sources. These public pages are what the quotes on this listing come from.
Product
OpenRefine
https://openrefine.org/Pricing
OpenRefine download
https://openrefine.org/downloadDocumentation
OpenRefine release 3.10.1
https://github.com/OpenRefine/OpenRefine/releases/tag/3.10.1