Kofax became Tungsten Automation on 16 January 2024, and the whole capture stack renamed with it. The part nobody tabulates: the rename is also a support boundary. Kofax Capture 11.1 has been in limited support since 3 March 2026 and reaches end of support on 3 March 2027.
Upload a document to extract
Drop files here or click to upload
Up to 50 files
Free plan extracts the first 5, rest can be unlocked after
Uploading...
Run the document type your worst batch class handles and compare the fields you get back.
Kofax Capture is now sold as Tungsten Capture. Kofax the company became Tungsten Automation on 16 January 2024, taking its name from the Tungsten Network business it had acquired in 2022. The capture stack renamed with it: Kofax Transformation Modules became Tungsten Transformation, Kofax VRS became Tungsten VRS, Kofax TotalAgility became Tungsten TotalAgility. Nothing was discontinued at the point of the rename, and Tungsten's own FAQ says plainly that "There will be no change or impact to products or services you currently use."
The part that matters if you run it: the rename also marks a support boundary, and the Kofax-branded side of it is already past its first date. Kofax Capture 11.1 entered limited support on 3 March 2026 and reaches end of support on 3 March 2027. Kofax Transformation Modules 7.1 entered limited support on 9 May 2026 and ends 9 May 2027. The Tungsten-branded successors run to 2028 and 2029, and Tungsten Capture 11.2 has no announced end date at all.
Last updated August 2026. Rename date and quoted sentences are from Tungsten Automation's press release and FAQ. The product name map is from the live tungstenautomation.com product pages. Support dates are from a Tungsten partner's published release and sunset schedule, cross-checked against a second partner's historical table.
Tungsten's rename FAQ answers the corporate questions but deliberately does not publish a product mapping table, which is why so many people end up searching for both names. The map below is taken from the live product pages rather than from the FAQ.
| Legacy Kofax name | Current name | What changed |
|---|---|---|
| Kofax Capture | Tungsten Capture | Same product line. Tungsten describes it as an enterprise document scanning solution that "ingests, classifies and extracts data and turns it into actionable insights for further processing". |
| Kofax Transformation Modules (KTM) | Tungsten Transformation | The classification and extraction layer that runs on top of Capture. Tungsten now names it as the embedded AI that pairs with Capture. |
| Kofax VRS | Tungsten VRS | The image cleanup engine, which "intelligently cleans, rotates, crops and straightens documents before data is extracted". |
| Kofax TotalAgility | Tungsten TotalAgility | The flagship platform combining intelligent document processing, low-code process design and RPA. Current release 2025.2. |
| Kofax Import Connector | Tungsten Import Connector | The email, fax and folder intake connector. Current release 2025.1. |
| Kofax Power PDF | Tungsten Power PDF | The desktop PDF line, which is a separate product family from capture. Current release 2025.3. |
| Kofax ReadSoft | ReadSoft | Still a named product offering. Standard support for ReadSoft is reported to have ended 31 December 2025. |
| Kofax (the company) | Tungsten Automation | The legal entity changed its name on 16 January 2024. Atalasoft, Printix, Ephesoft, ReadSoft and Tungsten Network all continue as product offerings. |
Two of these dates have already passed. If you are on Kofax Capture 11.1 or KTM 7.1, you are in limited support today, with roughly seven and nine months respectively until end of support.
| Product and version | Limited support starts | End of support | Status, August 2026 |
|---|---|---|---|
| Kofax Capture 11.1 | 3 March 2026 | 3 March 2027 | In limited support now |
| Kofax Transformation Modules 7.1 | 9 May 2026 | 9 May 2027 | In limited support now |
| Kofax Import Connector 2.11 | 4 March 2027 | 4 March 2028 | In full support |
| Tungsten Capture 11.2 | No date announced | No date announced | No end date announced |
| Tungsten Transformation Modules 2025.1 | 11 March 2028 | 11 March 2029 | In full support |
| Tungsten Import Connector 2025.1 | 16 January 2028 | 16 January 2029 | In full support |
These dates come from a Tungsten Automation partner's published release and sunset schedule. Tungsten maintains the authoritative version behind its own knowledge base and support portal, so confirm your specific entitlement there before you commit budget. We publish them because they are consistent with the documented historical cadence shown below and because no vendor-neutral page tabulates them at all.
Most coverage of the Kofax rename treats it as a marketing story: new logo, same software, nothing to do. That is true of the rename itself, and Tungsten says so directly. What it misses is that the products carrying the old name and the products carrying the new one are on different sides of a support schedule.
Every version still branded Kofax is now in its final phase. Kofax Capture 11.1 has been in limited support since 3 March 2026, with end of support on 3 March 2027. Kofax Transformation Modules 7.1 followed on 9 May 2026, ending 9 May 2027. Cross the naming line and the picture inverts: Tungsten Transformation Modules 2025.1 runs to 11 March 2029, Tungsten Import Connector 2025.1 to 16 January 2029, and Tungsten Capture 11.2 carries no announced end date.
That makes the name on your install a rough proxy for your support position. If your documentation, your license file and your Batch Manager all say Kofax, you are on the side of the line with a date on it. It is not an emergency, and it is not end of life, but it is a budget item with a deadline rather than an open-ended arrangement.
A published partner table for the older releases shows the pattern the newer dates follow: general availability, then limited support three years later, then end of support one year after that.
| Version | GA | Limited | End |
|---|---|---|---|
| Kofax Capture 11.0 | 20 Sep 2017 | 20 Sep 2020 | 20 Sep 2021 |
| Kofax Capture 10.2 | 27 Feb 2015 | 27 Feb 2018 | 27 Feb 2019 |
| Kofax Capture 10.1 | 29 Aug 2014 | 19 Oct 2017 | 19 Oct 2018 |
| Kofax Capture 10.0 | 13 Dec 2012 | 19 Oct 2017 | 19 Oct 2018 |
| Kofax Capture 9.0 | 18 Jan 2010 | 19 Oct 2017 | 19 Oct 2018 |
The same partner notes that Kofax "has supported 3 versions of their capture platform before pushing a version into end of life, but that policy has changed with the release of version 11.0".
A long-running capture estate accumulates names. Purchase orders say Kofax Image Products, the server says Ascent Capture, the support contract says Kofax, and the vendor's website now says Tungsten. All four can be correct at once.
Founded by two engineers who had worked together at FileNet, the company spends its first two decades as a scanning and image-processing specialist, which is why "Kofax Image Products Inc" still turns up in procurement records and asset registers.
The product shipped as Ascent Capture through version 7.5. The name changed at version 8.0, which reached general availability on 16 April 2008 and left support on 1 January 2013. Batch classes built before the change are still labelled Ascent, which is why both names turn up in the same estate.
The acquisition of the invoice network completed in 2022 and supplies the name the whole company would later take.
Announced 16 January 2024. The press release opens: "Today marks the beginning of an exciting new chapter in our nearly 40-year history: Kofax is now Tungsten Automation."
Kofax Capture 11.1 entered limited support on 3 March 2026 and Kofax Transformation Modules 7.1 on 9 May 2026. Both dates have already passed.
Kofax Capture 11.1 reaches end of support on 3 March 2027, and Kofax Transformation Modules 7.1 on 9 May 2027.
Tungsten's own documentation portal still serves version 11.1 as "Kofax Capture Documentation", under the product code KC, on a tungstenautomation.com address. So the marketing site says Tungsten Capture while the manual for the version you are running says Kofax Capture. If you have been second-guessing which name is current, that is why, and you were reading both correctly.
The Department of Veterans Affairs Technical Reference Model publishes a public entry for "Tungsten Capture (formerly Kofax Capture)". In the decision dated 14 February 2025, current 11.x versions are listed as authorized with constraints and flagged for divestment, versions 8.0 through 10.2 require a plan of action and milestones, and all versions become unauthorized by the third quarter of 2026.
This is one agency's own policy, not a vendor statement and not a government-wide ruling, so it does not tell you anything binding about your own environment. It is worth knowing anyway, because federal reference models tend to move ahead of commercial procurement on this kind of decision, and because "divestment required" is a clearer signal about a platform's trajectory than any lifecycle table.
If you are looking at options rather than just a version upgrade, the first question is not which vendor. It is whether you still need a capture platform at all.
A capture platform owns the physical side of the process: scanner operation and VRS image cleanup, batch class design, multi-function device and mailroom intake, operator workstations, and the routing of exceptions between them. If paper physically arrives in your building and running the scanners is part of the job, that is a real requirement and an API does not cover it.
A modern extraction API reads layouts it has never seen without a batch class or a trained template, returns structured fields with per-field confidence, and runs from a single REST call. There is no capture server to size, no designer to learn, no separate transformation module to license, and no version whose limited support date you have to diary.
DocuOCR is a cloud product. For a workload whose documents cannot leave your network, we are not the swap for an on-premises Kofax Capture install, and we would rather say so than sell around it. If the real constraint is control and auditability rather than physical location, that is a solvable conversation about data handling terms.
Kofax Capture 11.1 and Tungsten Capture 11.2 are one version apart and sit on opposite sides of a support boundary. 11.1 is in limited support with an end-of-support date of 3 March 2027. 11.2 has no announced date. Check the Batch Manager or Administration module before you plan anything.
Capture and Transformation have their own schedules and they do not line up. Kofax Transformation Modules 7.1 entered limited support on 9 May 2026, about two months after Capture 11.1 did. A site can be current on one and behind on the other.
For Kofax Capture 11.1 that date is 3 March 2027, which lands inside the next fiscal year for most US buyers. A version move needs a budget line and a test window, and neither appears if the date only lives in an engineer's head.
Many Kofax installs were designed when scanning paper was the hard part. If most of your volume now arrives as PDFs and email attachments through the Import Connector, you may be maintaining scanners, batch classes and a transformation project to solve a problem that has largely gone away.
Take the document type with the batch class nobody wants to touch, the one that breaks whenever the vendor changes their layout, and run it through a template-free extractor. That single test tells you more about your options than a migration deck will.
DocuOCR classifies a mixed file, reads layouts it has not seen before without a batch class or a template, extracts the fields you define, validates them, routes low-confidence reads to a built-in reviewer your own team operates, and exports through a dashboard or one REST API. There is no capture server to size, no transformation project to maintain, and no version whose limited support date you have to track. Pricing is published and self-serve, which is a different commercial model from a quoted enterprise license plus annual maintenance.
What we are not: DocuOCR is a cloud product, so it does not replace an on-premises install for a workload whose documents cannot leave your network, and it does not drive scanners or run mailroom batch operations. If your Kofax deployment exists because paper physically arrives in your building, you need a capture platform, and the honest answer is Tungsten Capture 11.2 or a comparable platform rather than an API. If most of your volume now arrives as PDFs and email attachments, the platform underneath it may be solving a problem you stopped having several years ago.
Take the document type that breaks every time a vendor changes their layout, run it through DocuOCR, and look at the fields and confidence scores that come back. That tells you more about your options than a migration deck.
Kofax alternative
The vendor-switch comparison in full
What is Kofax
The company and its product stack explained
OpenText Captiva
The same rename story, one vendor over
IBM Datacap alternative
The other long-running capture platform
Hyland OnBase alternative
Enterprise content services with capture
Intelligent document processing
What replaced template-based capture
