Meshy Remesh lowpoly Retires Oct 30 - Indie Migrate Worksheet 2026

If you searched meshy remesh lowpoly retire after the Meshy docs banner landed, you do not need another “AI 3D changelog” skim. You need a fill-in migrate worksheet that locks six decisions before October 30, 2026 — when model_type: "lowpoly" stops working and requests error:

Inventory — every script, notebook, Zap, and hardcoded JSON that still sends "lowpoly"
Replacement contract — smart-topology + meshy-t2 (+ target_polycount when you need a face budget)
Lab smoke — one Text-to-3D and/or Image-to-3D task on the new pair before you touch CI
Remesh / export path — Remesh API still in the Game Assets pipeline; prove GLB/FBX after the switch
Credit + topology honesty — Smart Topology preview pricing and triangle-only limits written down
Cliff latch — MIGRATE_DONE / HOLD_LIVE / ESCALATE before the retirement date

This URL is that worksheet. It is not the 12 free Meshy remesh tools after 7.1 Ultra 4K (poly-budget toolkit). It is not the Smart Topology keep/hold evening (first topology smoke). It is not the AutoRemesher free evening (offline quad remesh). Those own toolkits and first evenings. This URL owns the Oct 30 lowpoly retirement migrate with gates outsiders can footnote.

Why this matters now

Meshy’s API docs banner is blunt: lowpoly retires Oct 30, 2026. Please switch models before these dates to avoid request errors. The same warning appears on the Remesh API, Text to 3D API, and Image to 3D API surfaces teams actually bookmark.

Official Text / Image to 3D docs state that model_type: "lowpoly" is deprecated, retiring on October 30, 2026, and that after that date requests with model_type: "lowpoly" return an error. Meshy recommends switching to Meshy T2: model_type: "smart-topology" with ai_model: "meshy-t2". When lowpoly is selected today, parameters like ai_model, topology, target_polycount, and should_remesh are ignored — which is exactly why silent “we thought we remeshed” bugs show up in pipelines that still hardcode the old type.

October 12 → October 30 is a short calendar. Discord will invent “we’ll fix it on the 31st.” Request errors do not wait for your sprint board.

Direct answer: Fill Sections A–E this week. Grep the repo for lowpoly. Switch generation calls to smart-topology + meshy-t2. Smoke one remesh/export. Latch MIGRATE_DONE before Oct 30 — or HOLD_LIVE with a written freeze on new lowpoly jobs.

Who fills this worksheet

Audience	Outcome
Beginners	Know which JSON field to change before the cliff
Developers	Inventory scripts + CI + credit notes
Creators	Discord paste that stops “ship Ultra, ignore lowpoly”
Companies	CapEx / diligence language for vendor model retirement

Time: 45–75 minutes inventory + one lab smoke; longer if many services hardcode lowpoly.
Honest limit: Docs can add more retirement banners — re-read Text to 3D and Image to 3D before you quote partners. Smart Topology with meshy-t2 outputs triangles; do not combine it with topology: "quad" expectations. This worksheet migrates model_type: "lowpoly" — it is not a free Ultra 4K budget night (remesh tools listicle).

Non-repetition

URL	Job
12 free Meshy remesh tools after 7.1 Ultra 4K	Free poly-budget toolkit
Smart Topology keep/hold	First Smart Topology evening
Meshy 7 image-to-3D alignment smoke	Alignment keep/hold
AutoRemesher free evening	Offline quad remesh
AI 3D import-ready checklist	Broad import gates
This URL	Oct 30 `lowpoly` retire migrate worksheet

Pair art handoff with the Blender for game assets pipeline and 15 free Blender addons for game asset creation. Import pain stays in help: AI-generated assets not importing in Unity.

Official facts you must quote (not invent)

From Text to 3D and Image to 3D (banner also on Remesh):

Banner: lowpoly retires Oct 30, 2026 — switch models or request errors.
model_type: "lowpoly" is deprecated and retiring October 30, 2026.
After that date, model_type: "lowpoly" → error.
Recommended replacement: smart-topology + meshy-t2.
Under lowpoly today, ai_model / topology / target_polycount / should_remesh (and Image-to-3D save_pre_remeshed_model) are ignored.
meshy-t2 Smart Topology: cleaner topology, natively separated parts, triangle output, face count via target_polycount (docs range 100–15,000, default often 4,000 — verify live docs).
Remesh remains a separate API for remesh/export of existing Meshy tasks / model URLs — still use it in Generate → Remesh → texture pipelines, but stop feeding generation with retired lowpoly.

Pasteable diligence line:

We are migrating all Meshy generation calls off model_type: "lowpoly" to smart-topology + meshy-t2 before the Oct 30, 2026 retirement. Inventory grepped; lab smoke green; receipt filed. Live CI will not send lowpoly after migrate latch.

Section A — Cliff lock (fill in)

Field	Your answer
Studio / product	____
Cliff date	2026-10-30 (docs)
Days remaining (from fill date)	____
Owner	____
Repos / services that call Meshy	____
Decision goal	MIGRATE_DONE / HOLD_LIVE / ESCALATE

A-gate: If you cannot name every service that can POST to Meshy, inventory is incomplete — do not claim MIGRATE_DONE.

Section B — Inventory (fill in)

Grep patterns (adapt to your stack):

"lowpoly"
model_type.*lowpoly
model_type: "lowpoly"
model_type: 'lowpoly'

Location	Path / job	Still sends lowpoly?	Owner
CI / CD	____	Y/N	____
Local scripts	____	Y/N	____
No-code / Zap	____	Y/N	____
Docs / runbooks	____	Y/N	____
Teammate forks	____	Y/N	____

B-gate: Zero unknown Y rows before live cutover.

Section C — Replacement contract (fill in)

Field	Old	New (write yours)
`model_type`	`lowpoly`	`smart-topology`
`ai_model`	(ignored under lowpoly)	`meshy-t2`
`target_polycount`	(ignored)	____ (e.g. 4000)
`topology: "quad"` expected?	maybe folklore	No with meshy-t2 Smart Topology — triangles
Text to 3D endpoints updated?		Y/N
Image to 3D endpoints updated?		Y/N
Remesh after generate still used?		Y/N — path ____

Example payload shape (verify against current docs before paste into prod):

{
  "model_type": "smart-topology",
  "ai_model": "meshy-t2",
  "target_polycount": 4000
}

C-gate: Written contract reviewed by the person who pays API credits.

Section D — Gates M1–M8 (pass / fail)

Gate	Check	Pass if…	Result
M1	Docs re-read	Banner + retirement date confirmed this week	☐
M2	Inventory complete	Grep + table; no unknown callers	☐
M3	Code switch	No live path still defaults to `lowpoly`	☐
M4	Lab Text-to-3D	One SUCCEEDED task on smart-topology + meshy-t2	☐
M5	Lab Image-to-3D (if used)	One SUCCEEDED task on new pair	☐
M6	Remesh / export smoke	Remesh or download → engine import once	☐
M7	Credit note	Preview/credit expectation written	☐
M8	Cliff latch	MIGRATE_DONE before Oct 30 or HOLD with freeze	☐

Fail closed: M2 or M3 fail → no “we’re fine” Slack. M8 fail after Oct 29 → treat as incident.

Pattern gallery

Pattern	Usually…
Hardcoded `"lowpoly"` in one Python client	Migrate that client; M4 smoke
Shared SDK defaulting to lowpoly	Change default + version bump all consumers
“We only use Remesh, not generate”	Still re-read banner; inventory Image/Text callers in other teams
Expecting quads from meshy-t2 Smart Topology	Fail — triangles; offline remesh if quads required
Waiting until Oct 31	Fail — errors start on retirement

Section E — Decision latch

Circle one:

MIGRATE_DONE — M1–M8 green; live sends smart-topology + meshy-t2 only
HOLD_LIVE — freeze new Meshy jobs that need lowpoly; migrate in lab only until green
ESCALATE — credits / contract / multi-team inventory blocked; named exec owner

Owner: ____
Date: ____
Receipt: docs/meshy_lowpoly_retire_migrate_receipt_v1.json

Beginner path — 60 minutes

Prerequisites: Meshy API key with enough credits for one lab generate; ability to edit the script that calls Text or Image to 3D.

Open Text to 3D — write: lowpoly retires Oct 30 → error.
Open Image to 3D — same banner; note recommended smart-topology + meshy-t2.
Grep your project for lowpoly (Section B).
Change one lab script to the replacement contract (Section C).
Run one lab task to SUCCEEDED. Download / Remesh once if that is your ship path (Remesh API).
Import GLB once into your engine (or Blender).
Fill M1–M8. Paste Discord. Save receipt.

Common beginner mistakes:

Mistake	Fix
Only changing comments, not `model_type`	Grep again; fail M3
Keeping `lowpoly` “for cheaper” past Oct 30	It errors — migrate
Assuming remesh tools listicle is this migrate	Different URL — do both if needed
Expecting quads from meshy-t2	Use offline remesh / AutoRemesher evening
Skipping Image-to-3D when only Text was updated	Inventory both APIs

Developer path — pipeline depth

Why lowpoly ignored your remesh flags

Under model_type: "lowpoly", docs say several remesh-related parameters are ignored. Teams that set should_remesh or target_polycount while still on lowpoly were never getting the remesh behavior they thought. Migration to smart-topology + meshy-t2 is also a honesty reset: set polycount explicitly and re-smoke.

Remesh API after migrate

Remesh still remeshes completed Image/Text/Retexture tasks or model_url uploads. Keep Remesh in Generate → Remesh → AI Texturing style pipelines (Game Assets spirit). Do not confuse Remesh endpoints with the retired generation model_type.

CI checklist

Fail the build if "lowpoly" appears in Meshy request fixtures after migrate date.
Snapshot one golden lab task ID on smart-topology.
Alert on Meshy 400 spikes the week of Oct 30.
Pin docs changelog review in the calendar for Oct 20 and Oct 29.

Credit note (write numbers from live Pricing)

Smart Topology preview credit costs differ from older lowpoly / standard paths — record what your seat shows this week in M7. Do not invent prices in the receipt; paste the Pricing page date you checked.

Two-week calendar (print beside the cliff)

When	Action
This week	Grep inventory; assign owners; lab M4/M5
~Oct 20	Re-read docs changelog; confirm no new retirement banners
~Oct 27	Freeze new features that touch Meshy request shapes
Oct 29	Final grep — zero `lowpoly` in live paths; M8 latch
Oct 30	Watch API 400s; incident channel ready

If your release train cannot ship a config change between now and Oct 30, HOLD_LIVE means stop enqueueing lowpoly jobs immediately — not “hope the vendor slips.”

Shared SDK / monorepo tip

Bump the shared Meshy client once. Force consumers onto the new default (smart-topology + meshy-t2). Add a unit test that fails if any request builder still emits "lowpoly". One library change beats six silent forks.

Quad requirement?

If tooling or artists require quads, plan an offline remesh night (AutoRemesher or remesh tools) — do not fight meshy-t2 triangle output on Oct 29.

MIGRATE / HOLD / ESCALATE scripts

MIGRATE_DONE:
“All Meshy callers off model_type: lowpoly. Live uses smart-topology + meshy-t2. M1–M8 green. Cliff owner: ____.”

HOLD_LIVE:
“Freeze new lowpoly-dependent jobs. Lab migrate only. Live unchanged until M2–M6 green. Re-eval: ____.”

ESCALATE:
“Multi-team inventory incomplete / credits blocked. Exec owner: ____. No claim of MIGRATE_DONE.”

Discord / Slack paste

Meshy lowpoly retire migrate worksheet locked.
Cliff: Oct 30, 2026 — model_type "lowpoly" → errors after that date.
Replacement: smart-topology + meshy-t2 (+ target_polycount ____).
Inventory grep: ____ remaining lowpoly callers.
Gates M1–M8: ____ | Decision: MIGRATE_DONE / HOLD_LIVE / ESCALATE
≠ Ultra remesh toolkit / Smart Topology first evening — this is the cliff migrate.
Receipt: docs/meshy_lowpoly_retire_migrate_receipt_v1.json

Worked evenings

Studio A — one Python client

Grep finds one "lowpoly". Switch + M4 smoke + Remesh. MIGRATE_DONE same day.

Studio B — three microservices

Two updated, one Zap still on lowpoly. HOLD_LIVE until Zap fixed; fail M2.

Studio C — “we only Remesh”

Separate team still generates with lowpoly. Shared diligence: escalate inventory. ESCALATE.

Studio D — wants quads in-engine

Migrate to meshy-t2 triangles; schedule AutoRemesher evening for hero props. Do not keep lowpoly for quads past cliff.

Studio E — Ultra FOMO week

Ultra budget is the tools listicle. Still finish this migrate — Ultra does not cancel Oct 30 errors.

Failure modes

Failure	Looks like	Write
Post-cliff 400s	CI red Oct 30	Emergency switch + incident
Silent ignored remesh flags	Mesh not what you configured	Re-smoke on smart-topology
Missed Zap / notebook	One path still lowpoly	Re-grep; M2 fail
Quad surprise	Pipeline expects quads	Offline remesh plan
Credit shock	Unexpected preview cost	Update M7; adjust batch size

CapEx four-liner

Asset at risk: Automated prop generation + partner deadlines after Oct 30.
Change proposed: Migrate off model_type: "lowpoly" to smart-topology + meshy-t2.
Cost if wrong: Hard API errors mid-sprint; emergency engineer time; stalled art CI.
Decision owner: Tech art / platform lead; default = migrate before cliff.

Thirty-minute team agenda

0–5 — Read docs banner + retirement paragraph on Text + Image to 3D.
5–15 — Grep inventory; assign owners for each hit.
15–20 — Agree replacement contract (Section C).
20–25 — Schedule lab smokes M4–M6.
25–30 — Latch HOLD or commit MIGRATE date; paste Discord; file receipt stub.

Partner / contractor note

If an external contractor owns Meshy scripts, send them the diligence line and Section C table this week. Do not assume their template still defaults to standard — many 2025–2026 samples used lowpoly for “game-ready” marketing. Require a written M3 confirmation (PR link or screenshot of the request body) before Oct 27. Treat missing confirmation as HOLD_LIVE, not an informal verbal “we’ll update it.”

Receipt — `meshy_lowpoly_retire_migrate_receipt_v1.json`

{
  "receipt_type": "meshy_lowpoly_retire_migrate_receipt_v1",
  "filled_at": "2026-10-12",
  "cliff_date": "2026-10-30",
  "replacement": {
    "model_type": "smart-topology",
    "ai_model": "meshy-t2",
    "target_polycount": 4000
  },
  "inventory_remaining_lowpoly": 0,
  "decision": "MIGRATE_DONE",
  "gates": {
    "M1_docs": false,
    "M2_inventory": false,
    "M3_code_switch": false,
    "M4_text_lab": false,
    "M5_image_lab": false,
    "M6_remesh_export": false,
    "M7_credits": false,
    "M8_latch": false
  },
  "owner": "",
  "notes": "Distinct from Ultra remesh toolkit / Smart Topology first evening"
}

Key takeaways

lowpoly retires Oct 30, 2026 — docs banner + Text/Image to 3D.
After cliff, model_type: "lowpoly" errors.
Switch to smart-topology + meshy-t2.
Under old lowpoly, remesh-related params were ignored — re-smoke.
meshy-t2 Smart Topology → triangles, not quads.
Inventory grep ends “we’re probably fine.”
M1–M8 fail closed on live cutover.
Remesh API remains useful — different from generation model_type.
Ultra toolkit is a sibling, not a substitute.
CapEx prefers migrate-before-cliff over emergency Oct 30.
Beginners can finish one-lab migrate in ~60 minutes.
Primary keyword: meshy remesh lowpoly retire.

FAQ

What retires on October 30, 2026?

Meshy’s model_type: "lowpoly" on generation APIs (documented on Text to 3D and Image to 3D). After that date those requests error. Docs banner: switch models before the date.

What should I switch to?

Meshy recommends smart-topology with ai_model: "meshy-t2", optionally with target_polycount.

Does this break the Remesh API?

Remesh remains available for remeshing existing tasks / URLs (Remesh docs). The cliff is about generation model_type: "lowpoly". Still inventory any code that generates with lowpoly before Remesh.

Why does my title say Remesh if lowpoly is a model_type?

Searchers and the docs banner pair Remesh/API migration language with the retirement. This worksheet covers the migrate job for pipelines that generate then remesh/export — primary keyword meshy remesh lowpoly retire.

Is this the same as the Ultra remesh tools listicle?

No. 12 free Meshy remesh tools is a poly-budget toolkit. This URL is the Oct 30 retirement migrate worksheet.

Will existing lowpoly assets disappear?

Retirement targets new requests with model_type: "lowpoly". Already-generated assets stay in your downloads/storage per normal Meshy task rules — but your automation will break if it still sends lowpoly.

What primary keyword does this page target?

meshy remesh lowpoly retire.

What if we need quads?

Migrate off lowpoly first; use offline remesh/quad tools afterward — do not keep lowpoly past Oct 30 for topology folklore.

Conclusion

October 30 is a hard cliff for model_type: "lowpoly". Grep the callers. Switch to smart-topology + meshy-t2. Smoke Remesh/export once. Latch MIGRATE_DONE before the date — not after the first red CI build.