<- Back to news

Full-hand tactile sensing moves robot hands beyond vision-only control

A historical comparison of F-TAC Hand, Sparsh and Digit 360 separates coverage, visual sampling and task evidence for robot hand integrators.

full-hand tactile sensingF-TAC HandMeta SparshDigit 360
Illustration for Full-hand tactile sensing moves robot hands beyond vision-only control
Explanatory illustration for this brief; technical evidence is in the cited sources.

Historical news brief - June 2026. Evidence reviewed November 3, 2026.

Distributed touch can expose contacts at the palm and sides of fingers that fingertip-only sensing does not directly observe. The useful comparison is what those observations allow a controller to do. A sensor count, image scale and benchmark score answer different parts of that question.

Explore tactile sensing for the broader comparison.

Key data points

The F-TAC Hand paper was published on June 9, 2025. It describes 17 vision-based tactile sensors, approximately 70% hand-surface coverage and a calibrated visual scale of 0.1 mm per pixel. Its manipulation evaluation includes 600 trials across 60 object combinations. These are author-reported results from the study configuration; they do not establish complete surface coverage, a universal success rate or force-measurement accuracy. Nature Machine Intelligence paper.

Meta's October 31, 2024 announcement concerns separate projects. It describes Sparsh pretraining on more than 460,000 tactile images and a six-task benchmark. For Digit 360 it advertises over 18 sensing features, detection of forces as small as 1 mN and an optical field described as over 8 million taxels. Those are the publisher's terms and claims, not independently measured specifications or directly comparable counts of physical sensor modules. Meta FAIR announcement.

Published quantityWhat it describesWhat it does not establish
F-TAC Hand coverageActive sensing area on the reported handEvery task-relevant contact is observed
F-TAC Hand pixel scaleSpatial calibration of visual readoutForce accuracy or universal contact discrimination
F-TAC Hand trial countSize of the reported manipulation evaluationIndependent environments or arbitrary-object performance
Sparsh image countPretraining materialNumber of robot-action demonstrations
Digit 360 optical taxelsAn optical sensing description in Meta's announcementThat many separate calibrated force cells

RoboSkin analysis

These projects address different layers. F-TAC Hand integrates sensing with a hand and its behavior. Sparsh addresses representations learned from tactile images. Digit 360 addresses a multimodal fingertip; Digit Plexus is described as an integration platform. They should not be ranked on one density scale or treated as one experiment.

For an integrator, the important boundary is between available observations and observations actually used by the policy. More coverage can reveal a previously hidden contact, but it can also add acquisition, synchronization and processing work. Compare complete configurations under the same task instead of combining the best hardware number from one project with the best learning result from another.

What this means for robot hands

Map contact over the whole manipulation sequence: approach, initial grasp, repositioning, recovery and release. Mark active areas, seams and blind regions at the relevant joint positions. Then identify which estimate each contact supports and which action can use it.

The robot hand tactile sensor route owns the general coverage decision. For paper-specific hardware and measurement boundaries, use the F-TAC Hand interpretation. This news page provides historical context across projects rather than another full hardware guide.

What this does not prove yet

The phrase “vision-based tactile sensor” means that cameras can read deformation inside the contact sensor. It does not mean the robot must use an external scene camera, nor does it prove that scene vision is unnecessary. Removing a scene camera and removing all optical sensing are different claims.

Similarly, a force-detection threshold is not an accuracy bound, and a visual pixel scale is not a force threshold. A fair comparison names the reference, contact geometry, coordinate frame and error metric. The calibration guide develops that measurement record.

Where this fits next

The Dream-Tac tactile world model interpretation distinguishes predictive outputs from policy and timing results. The ROS 2 tactile data pipeline addresses a different requirement: observations must retain enough context to be synchronized and replayed. Neither linked article turns a hardware specification into a guaranteed task outcome.

Practical questions

  • What is the task's missing observation? Identify whether it is contact presence, location, direction, magnitude or motion before comparing density.
  • What is the evaluation unit? Keep object combinations, repeated trials, images and training episodes separate.
  • What changes after service? Record replacement, remounting and calibration changes before comparing a new run with the original result.
  • What happens when a channel is missing? State whether the controller detects the condition and which fallback has actually been evaluated.

What readers should take away

Choose coverage around the contacts and decisions that matter. A useful comparison record includes the installed configuration, observations consumed, timing boundaries, task denominator and failure cases. This is an editorial planning recommendation, not an additional F-TAC Hand or Meta experiment.

Source boundary

RoboSkin.ai reviewed the F-TAC Hand publisher article and Meta's dated announcement. All performance statements remain attributed to those sources. We did not run the hardware, download models, verify current procurement or licensing, or establish a service-life or safety claim. Historical release plans are not presented as current availability.

Sources

Continue the topic

Dexterous grasp controlWhole-hand force regulation tracks contact without tactile sensors