Google ⇄ Meta Feed Converter

Paste a feed with a header row. Values whose spelling differs get translated; values with no equivalent on the other side are left blank — with an explanation of what each possible substitute would actually cost you.

🔒 Your data never leaves your browser.

Header row required — that is how the columns are mapped.

Google has four stock values. Meta has two.

Google supports in_stock, out_of_stock, preorder and backorder. Meta supports in stock and out of stock. That is not a spelling difference — two of the four have nowhere to go.

And neither substitute is free:

That is a merchandising decision, and it belongs to you. A converter that quietly picks one looks more finished and has just decided something on your behalf — so this one leaves the cell empty and tells you what the choice is.

FieldMeaningGoogleMeta

What is copied across untouched

Most attribute names are shared, so they are carried over as they are. The target platform may still have constraints on the content of those fields:

Those are not enforced here, because this tool converts rather than validates. Run the result through the marketplace feed validator afterwards.

Why only these two platforms

Google and Meta both publish their field lists and value sets openly, so this conversion rests on data taken verbatim from their documentation. The other marketplaces keep theirs behind a seller login or change them each release. Converting to those would mean guessing — and a wrong conversion is worse than none, because it looks finished.

Every check this tool runs (6 rules)

CNV-N01 No equivalent value on the target platform

The source platform has a value the target does not. Google supports preorder and backorder; Meta supports only in stock and out of stock. There is no safe substitute — one oversells goods you do not have, the other refuses an order you would have taken — so this tool leaves the cell EMPTY and tells you what the choice is. A converter that fills it in has made a merchandising decision on your behalf.

Fix: Decide per product, then fill the blank cells before uploading.

Source: Google Merchant Center Help — Availability [availability]

CNV-T01 Value translated

The value means the same thing on both platforms but is spelled differently — in_stock with an underscore on Google, "in stock" with a space on Meta. This is the difference that silently breaks a reused feed.

Source: Meta — Catalog Fields

CNV-U01 Value not recognised on the source platform

The value is not one the source platform publishes, so there is nothing to translate it from. It is copied through unchanged, which is almost certainly not what you want — check it against the source platform first.

Source: Google Merchant Center Help — Condition [condition]

CNV-F01 Field carried across unchanged

Most attribute names are shared between Google and Meta, so they are copied as they are. Where the target platform has extra constraints on the content — image size, title length, plain-text description — they are listed on the page rather than enforced here, because this tool converts rather than validates.

Source: Meta — Catalog Fields

CNV-S01 Only Google to Meta is supported, deliberately

Both platforms publish their field lists and value sets openly, so a conversion between them can be built on verified data. The other marketplaces keep theirs behind a seller login or change them per release — converting to those would mean guessing, and a wrong conversion is worse than none because it looks finished.

Source: Meta — Catalog Fields

CNV-E01 No header row

The first line must name the columns; without it there is nothing to map.

Source: Meta — Catalog Fields

Both value sets are taken verbatim from the platforms’ own published pages. Where one platform has no equivalent, the cell is left blank rather than filled in.