Skip to main content
TabPFN-3.5 can use free-text columns together with the rest of your table to predict a target. For example, support ticket notes can contribute to churn predictions, reviewer notes to insurance claim predictions, and product descriptions to demand estimates.

Local package and API

Use a package release with TabPFN-3.5 support. See the quickstart for installation, authentication, and model selection.

Plus text limits

TabPFN-3.5-Plus text preprocessing supports at most 10 million tokens in total and 2,500 characters per text value. These limits apply in addition to the model’s row and column limits.

Pass a mixed table

Keep text in its original columns. You do not need to manually vectorize it before passing it to TabPFN-3.5. For a churn classification task, a customer dataset might contain: Load your data and split it into training and test sets:
Set text columns to the pandas string dtype so they can be detected as text, including on pandas 2. Declaring plan as category keeps it categorical regardless of how many distinct values it contains. Select TabPFN-3.5 locally or TabPFN-3.5-Plus through the API:
For a numerical target, use TabPFNRegressor from the same package. The feature table can still contain text, categorical labels, and numerical values.

Preparing text columns

  • Keep text features alongside the other relevant columns, so the model can use both the text and the structured data.
  • Use the same feature columns when fitting and predicting.
  • Include only text available at prediction time. For example, notes written after a customer churns should not be inputs to a prediction of that churn.
  • Start with raw text. Evaluate manual vectorization or domain-specific text features against that baseline on held-out data, and fit learned preprocessing only on the training split.
See Preprocessing for text-input guidance and Benchmarking for comparing models with different preprocessing.