Dental X-Ray Sensors in 2026: What to Buy and How IT Sets Them Up

"Image quality, durability, or software compatibility?" That was the question an owner put to other dentists in May 2026 while shopping for a new sensor. The quotes you get from reps all read alike: a resolution number, a warranty line, a bundle with positioners. None of them says whether the sensor will appear in your imaging program on Monday, which USB port it needs, or who you call when it does not.

This guide puts the sensors dental offices actually shortlist side by side, using only what each maker publishes on its own pages (all read on 6 November 2026), explains what the spec sheet means, and then covers the part the rep does not sell: the computer, Windows version, network and image storage the sensor depends on, and the order to do things on install day. It is written for an owner replacing a sensor or equipping new operatories. If a sensor that used to work has stopped since last night, that is a different problem, covered in our guide to a sensor or camera stopped after a Windows update.

What should you compare when buying a dental X-ray sensor?

Compare seven things: the resolution the maker states and whether it is measured or theoretical; the sizes offered; how the sensor connects to the computer; the cable and what happens when it breaks; which imaging programs the maker names; the driver statement for current Windows; and the warranty, loaner and repair terms in writing.

Most buying mistakes come from comparing the first item only. The table below is the decision frame the rest of this guide fills in.

Which dental X-ray sensors do practices buy in 2026, and how do they compare?

The sensors below are the ones dental offices most often shortlist. Every figure comes from the maker's own product page or requirements document, read on 6 November 2026; "not stated" means the page does not say. Where a maker labels resolution as theoretical, the table keeps that word, since it is not a measured figure.

Vendor pages read 6 November 2026. Specifications, bundles and warranty terms change; confirm each line with the maker before you order.

True, measured or theoretical: why the resolution numbers are not comparable

A theoretical resolution is calculated from the pixel pitch: the smaller the pixel, the higher the number. A true or measured resolution is what the maker says the finished sensor resolves on a test target, after the scintillator and optics have done their work. Carestream and Planmeca publish measured figures; Vatech, Dentsply Sirona and XDR publish theoretical ones. A 24 lp/mm measured sensor and a 33 lp/mm theoretical sensor are not 9 lp/mm apart, and the only fair comparison is sample images taken on your own X-ray head.

Grouped by the office buying them

• • Keeping an existing imaging suite. XDR and SOTA both name "Dexis, Eaglesoft, Patterson Imaging, Schick CDR, and more" as programs they integrate with, and Carestream states TWAIN compatibility for third-party software. If you want to keep your imaging program and replace only the sensor, start here, and confirm the version you run.
• • Buying the sensor and software from one maker. Carestream RVG with CS Imaging, Vatech HD Sensor with EzDent-i, Planmeca ProSensor HD with Romexis, Schick with Sidexis. One support line for capture problems, and one requirements document for your IT provider to build to.
• • Pediatric or small mouths. Carestream's CS 6200 Size 0, XDR's size-1 pediatric sensor and SOTA's Clio Pedo are the published small options; Vatech and Owandy also offer a 1.5 size that sits between the usual 1 and 2.
• • A startup fitting out several rooms. Prioritise cable replacement terms and a loaner program over the last few line pairs, because the sensor that fails will fail in the busiest room. The startup also has the chance to buy the imaging computers to the sensor maker's requirements rather than retrofitting; our guide to which computers to buy for a dental office covers that side.

Does the sensor have to match your imaging software?

Yes, in one of two ways. Either the sensor is a native device in the imaging program, or it connects through TWAIN, the standard driver interface imaging programs use to ask a capture device for an image. Both work; the difference is who sets it up, who supports it, and which quirks you inherit.

Open Dental's own compatibility page puts the TWAIN rule plainly: "Any sensor with a 32-bit TWAIN driver should be compatible, but we have not tested them all." Its tested list includes Carestream RVG, Schick, Vatech, XDR, DentiMax, Tuxedo and Woodpecker sensors, with Gendex owners told to "Contact Dexis for drivers or installation assistance"; SOTA Clio sits under "Untested Sensors". Dentrix describes its imaging module as offering "plug-and-play compatibility with more than 150 devices". Carestream says of its RVG line that "TWAIN compatibility lets you easily connect RVG sensors to third-party imaging software".

Three details from Open Dental's own pages save real time. In Open Dental, "Always set it to single capture", so control returns to the program after each image. Dexis sensors on the GxTwain driver need the word "Dexis" in the device description "otherwise xray images are inserted into mounts in reverse order". And when a capture fails, Open Dental's first step is a free TWAIN test tool (Twacker): if the fault repeats outside Open Dental, "the issue lies with the device or the device driver", which is the sensor maker's problem, not the software's.

The short version of this section: will this sensor work with our practice software and imaging program? That compatibility question is answered by the maker's support statement for your exact program and version, in writing, before the order. If the practice software itself is the thing you are choosing, the imaging decision follows it; our page on dental practice management software support describes how we look after both layers together.

Drivers have a lifecycle too

A sensor can outlive its driver. Open Dental's compatibility page notes, under Schick, that "As of 12/31/2024, Dentsply Sirona is discontinuing support for some drivers" and offers help obtaining them, which is what an orphaned driver looks like from the outside. Microsoft's lifecycle page says "Windows 10 will reach end of support on October 14, 2025", so a sensor you buy now will spend its life on Windows 11, and the question to put to the maker is a dated statement that the current driver is supported there. For DEXIS owners, the platform page for DEXIS IT support describes how we handle that layer.

Which sensor size do you need, and how many?

Most general offices run size 2 for adult bitewings and periapicals and size 1 for anterior views and smaller mouths; size 0 is a pediatric sensor, and a 1.5 is a middle size a few makers offer. Buy one sensor per operatory that takes radiographs, because sharing a sensor means moving the driver and the software with it.

The makers publish their sizes in different units, which makes a shopping list harder than it should be. Here they are side by side as published.

On sharing: Carestream's own RVG guide allows it, but the condition is the one offices skip. "Each workstation must have CS Imaging Software and corresponding drivers installed", and the sensor goes into "a USB 2.0 minimum port that is connected directly to the motherboard" on each PC. A sensor carried between rooms is also a sensor whose connector is plugged and unplugged several times a day, and the yomotherboard report of a Dentrix Ascend office whose system "usually reports a \"device error\" instead of detecting the new sensor" after switching sizes shows the kind of fault that appears when devices move. Specialists have their own layout questions; our guide to endodontic operatory imaging setup covers the endodontic version.

The IT side: what does a sensor need from your computers and network?

A sensor is a USB device that depends on four things it does not ship with: a port wired to the motherboard, a computer on a Windows version the maker supports, a network path to the image database, and a backup of that database. The maker's requirements document names each one; your IT provider should read it first.

The USB port

Carestream's guide is explicit for its RVG line: "To ensure the best quality images, you must connect the RVG sensor to a USB 2.0 minimum port that is connected directly to the motherboard (generally located on the BACK of the workstation)." Vatech's HD Sensor uses a "Direct interface with USB 3.0". Front-panel ports, keyboard ports and monitor hubs are where intermittent captures begin. If the kit ships a hub, as Carestream's RVG kits list "Two USB 2.0 Hubs", use the supplied one and nothing else. A small-form-factor PC with two rear ports fills up fast once a sensor, an intraoral camera and a signature pad are in the room; count ports before you count line pairs.

The computer and the Windows version

The imaging program sets the floor. Carestream's CS Imaging 8 requirements name "Windows 11, 64-bit" for workstations and add that the server "cannot be installed on Windows Home Edition" and that the program "is not designed for Windows touchscreens". Planmeca lists a Romexis client on "Windows 11 Pro (64 bit)". Vatech's EzDent-i viewing computer needs "Windows 10 Professional or Higher (64 bit)". With Windows 10 past its end of support since 14 October 2025, an imaging PC still on it is a replacement, not a candidate for a new sensor. Our guide to which computers to buy for a dental office covers the specification by room, and the dental servers and workstations page covers our workstation and server service.

The network and the image database

Images are captured in the room but live on the server. CS Imaging 8 asks for "network bandwidth (100Mb/s) for a 2D environment" and, where 3D volumes are present, "1000 BaseT network bandwidth (1Gb/s)"; a sensor-only office meets that on any wired gigabit network, a CBCT office needs the gigabit path to be real, which our guide to CBCT computer and network requirements explains. Henry Schein One's Dentrix requirements carry the line every imaging room should respect: "Wireless networks are to be used at your own risk due to potential interference from X-ray machines and other devices." Keep the imaging PC on a cable.

Backup and the deleted-image question

A sensor replacement is the moment people discover where the images actually are: a folder on the server, a database the imaging suite owns, or both. Before install day, confirm the image database is inside the nightly backup and that a restore has been tested; our guide to dental data backup sets out what that test looks like. If an image has already gone missing, our guide on a deleted patient file or X-ray covers what to try before calling anyone.

Where the sensor sits in the whole stack

The sensor is one layer of a practice's technology, and it breaks most often at the joins with the layers around it: port, driver, imaging program, bridge, storage. Our imaging integration troubleshooting guide shows where each join is and who owns it.

How do you install a new sensor without losing a morning?

Install in this order: confirm the computer and port, install the maker's driver on every workstation that will use the sensor, add the device in the imaging program, take test exposures on a test object, confirm the image saves to the server and opens on a second PC, then test the bridge from the practice software.

1. 1. Confirm the host PC the day before. Windows version on the maker's list, a rear USB port free and wired to the motherboard, the imaging program at a supported version, and the PC excluded from an update restart overnight.
2. 1. Install the driver on each workstation that will use the sensor. Carestream's rule applies to every maker: the software and "corresponding drivers" go on each PC, not only the first one.
3. 1. Add the device in the imaging program. In Open Dental that is Setup, Imaging, Devices, with "Show Twain UI" checked and single capture selected; in a suite it is the maker's device setup. Give each sensor and size a clear description, including the maker's name where the manual asks for it.
4. 1. Expose a test object, never a patient. Use the maker's test target or a phantom to confirm capture, orientation and mount order for every size you bought.
5. 1. Confirm the save path. Open the test image on a second workstation and on the server. If it opens in the room only, the storage path is wrong and the first real exposure will vanish into a local folder.
6. 1. Test the bridge. Open a test patient in the practice software, launch imaging from the chart, capture, and confirm the image lands on that patient. Our dental imaging integration troubleshooting guide has the layer-by-layer check if it does not.
7. 1. Record the install. Sensor serial, size, room, computer name, driver version and installer location, warranty start date and the maker's support number, in one document your IT provider holds.
8. 1. Back up that night and check the log. The first backup after a new imaging device confirms the database or folder is included.

Steps 1, 2, 5 and 8 belong to IT; 3, 4 and 6 are shared with the maker's installer; 7 is the one everyone forgets and the one that saves the warranty call.

What does a dental X-ray sensor cost, and what drives the price?

Most makers' product pages carry no list price; sensors are usually quoted through dealers and often sold as kits of two sizes with positioners, hubs and sheaths. The price you compare should include the imaging software licence if any, the warranty or club program, cable replacement, and the imaging computer the sensor needs, because that last item is the one quotes leave out.

Of the maker pages read for this guide, only one online shop showed prices, and only for kits. This guide quotes no dollar figures, because kit contents, promotions and dealer terms move the number more than the sensor does. What the pages do show is how the price is structured:

• • Kits versus singles. Carestream's shop lists two-sensor kits ("Get two RVG 5200 sensors for one low price!") with positioners, hubs, wall mounts and sheaths included. A single-sensor quote and a kit quote are not comparable until you list the contents.
• • Software and licences. Some sensors assume the maker's imaging suite; some ship a TWAIN licence; some are sold into the suite you already own. Ask what the quote assumes.
• • Warranty programs. XDR publishes a four-year, zero-deductible warranty and a club membership with "lower-cost replacements, cord replacement savings, sensor loaners, and expedited service"; SOTA publishes two years with loaners. A longer published term shifts cost from year three onward into the purchase price, which is a fair trade if your failure history says you will use it.
• • The cable. A field-replaceable cable (SOTA; XDR's "replaceable, Kevlar-reinforced cord"; Dentsply Sirona's in-house exchange) turns the most common failure into a part, not a return.
• • The computer. A sensor that needs Windows 11 in a room still on Windows 10 costs a sensor plus a PC. Budget them together.
• • Timing. Equipment bought and put into service before the year end may be treated differently from equipment bought in January; ask your accountant how the year-end rule applies.

When should you repair a sensor and when should you replace it?

Repair under warranty, and replace when the same sensor has failed twice outside warranty, when the maker no longer supports its driver on your Windows version, or when a fault follows the sensor from room to room while other sensors work in the same rooms. Keep a one-line failure log so the decision is made on dates, not memory.

The log is simple: date, room, sensor serial, what the imaging program said, what fixed it. After three months it answers questions a rep cannot. A fault that follows the sensor is the sensor; a fault that stays in one room is the PC, port or driver; a fault that appears across rooms on the same morning is almost always an update, which is the ground our sensor or camera stopped after a Windows update guide covers. Published durability claims help you set expectations without over-trusting them: Carestream states cables "tested for over 100,000 flexions—or 10 years of intense use under normal conditions", and SOTA states a replaceable cable with "loaner sensors during any repair". Hold the maker to the written term.

What to verify before you sign

Sensor demos look alike on a demo PC. These checks separate the quotes, and every one can be asked for in writing.

1. 1. Software support statement. The sensor model and each size you are buying, supported with your imaging program at the version you run, dated.
2. 1. Driver statement. Windows 11 support for the driver, dated, with the download location.
3. 1. Resolution basis. Whether the figure is true or measured versus theoretical, and sample images at a bitewing exposure on your own X-ray head.
4. 1. X-ray source compatibility. Carestream states its RVG sensors are "NOT compatible with X-ray sources that have a voltage LESS THAN 60 kV" and recommends 60 to 70 kV; ask every maker the same question about the heads you own.
5. 1. Connection and hub rules. USB version, whether a control box is involved, and whether a hub or extension is supported or supplied.
6. 1. Cable terms. Replaceable or not, price of a replacement, turnaround, and whether a loaner is sent.
7. 1. Warranty in full. Years, deductible, what counts as a defect, whether coverage transfers with a change of ownership, and the cost of any club or extension.
8. 1. Regulatory status. The maker's 510(k) number for the sensor; intraoral digital sensors are listed by the FDA under product code MQB, "Solid State X-Ray Imager (Flat Panel/Digital Imager)", a Class II device, and the number can be checked in the FDA's public database.
9. 1. Kit contents. Positioners, hubs, mounts, sheaths and whether both sizes are in the box.
10. 1. Who installs and who supports. Which party installs the driver on each PC, who answers a capture fault on day 30, and whether your IT provider is allowed on the support call.

What to ask your IT provider before you buy a sensor

How Legend Networking can help

Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004. Legend supports the IT environment for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, and for the practice software Dentrix, Eaglesoft, Open Dental and Archy, which is where sensor drivers, image storage and bridges live. Onsite dispatch is by appointment across served dental markets, and support is remote-first nationwide.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. You can see the kind of installation this guide describes in a recent practice buildout covering network infrastructure, imaging systems, workstations and Wi-Fi, and our page on dental software and imaging support in Dallas covers the local version of this work.