Airtable documents a specific paste limitation
Airtable supports Markdown-like rich text in several parts of the product, but its own documentation makes an important distinction: in a rich long-text field, Markdown syntax must be entered directly in Airtable. Copied and pasted text is not recognised as Markdown syntax. That means a perfect Markdown string on the clipboard can still arrive with visible asterisks and brackets.
This is not a cleanup failure. It is a destination contract. A converter should not claim that copying Markdown into an Airtable long-text cell will create rich formatting when Airtable says it will not.
Typed Markdown, pasted text and API values are different routes
Airtable's support table separates base descriptions, long-text fields, automations, the web clipper and the API. Those surfaces do not share one set of Markdown features. Bold and labelled links, for example, may work in one route and not another. The right output therefore depends on how the text reaches Airtable, not just on the word Airtable.
For one short note, a clean plain-text paste may be the most honest choice. For repeatable rich content, an automation or authenticated API connector can use the representation Airtable documents for that route. That is a different product capability from clipboard formatting and should be presented as such.
| If you need to | Use this route |
|---|---|
| One note in one long-text cell | Paste readable plain text and apply important formatting inside Airtable. |
| Many rows and columns | Use tab-separated text, CSV or Airtable's import workflow. |
| Repeatable rich field values | Use a tested automation or API connector with explicit field mapping. |
| Files and attachments | Upload or map them as Airtable attachments, not inline document content. |
Tables usually belong in fields, not one rich-text cell
A copied document table describes rows and columns. Pasting that entire table into a long-text field discards the most useful part of Airtable: each value having its own field type. A stronger conversion turns the source table into a previewable set of records and fields.
Tab-separated values are useful for a quick grid paste. CSV is useful for a file import. A connector is useful when column mapping, select options, dates, attachments or linked records need validation. Pasteful does not currently claim to perform this structured Airtable conversion. It is tracked as a separate product gap because silent field guessing would be risky.
- Preview source columns before writing records
- Choose how blank values and extra columns are handled
- Keep select options, dates and numbers typed correctly
- Never turn a name into a collaborator field without confirmation
- Report rows that could not be mapped
What Pasteful can do safely today
Pasteful can remove hidden characters, normalise spacing and produce readable plain text before an Airtable paste. It can also preserve portable Markdown for a different destination. It does not label a current rich clipboard output as Airtable-compatible because the documented long-text paste behaviour does not support that promise.
The planned Airtable route is more useful than another generic rich-text preset: structured table output with TSV and CSV, followed later by an optional connector with a field-mapping preview. Until those checks exist, the safe path is to paste plain text or use Airtable's own import and automation routes.