Quick answer
A base is a starting file, not a finished deliverable. Owning or buying a base does not automatically mean an artist can cheaply edit it for streaming, VRChat, a game, or resale. You still need to know three things before anyone quotes: license, file type, and target fit.
Wrong assumption
"You can just edit my base — should be quick." That sentence hides everything. A texture swap on a clean VRoid you own is not the same job as retopoing a Daz export, re-rigging a marketplace FBX, or untangling a stitched commission someone else built. Same words from you — very different invoices from the artist.
How this page fits the cluster
- This page: you are starting from a file you already have.
- Your model is a Frankenstein: the file is already a mashup of parts — edits get painful fast.
- Small edits are not always small: the change sounds tiny; the systems underneath may not be.
- Source files are not always included: an export you can open is not always a file an artist can actually edit.
Same phrase, different situations
When you say "I have a base," which row sounds like you?
| What you might mean | What you might actually have | Work still on the table |
|---|---|---|
| "I made it in VRoid" | Legitimate VRM starter you own | Custom silhouette, outfits, optimization, VRChat upload if that is the target — VRoid is a starter path, not fully custom design |
| "I bought a base on Booth / a store" | Licensed marketplace mesh | Confirm commercial and streaming rights; style fit; rig and poly fit for your platform |
| "It is a Daz / MetaHuman export" | Fast humanoid block-in | Cleanup, retopo, re-rig, license limits — often far more than a texture pass |
| "My last artist sent me the files" | Prior commission export — maybe not source | Revision rights, editable layers, whether the next artist inherits a mess — see Frankenstein page |
| "It is kitbashed / mixed parts" | Frankenstein already in progress | Integration owner, license chain, and likely rebuild scope — not a quick edit |
Three checks before you assume savings
Run these before you argue about price. If you cannot answer them, the quote will be a guess.
1. License — can you use it this way?
- Personal stream, commercial client work, merch, resale, and third-party edits are different permissions.
- "I bought it" or "I own the file" is not the same as "an artist can modify and deliver it for my use case."
- Send the license link or PDF with the base, not after the artist opens the mesh.
2. File type — can an artist actually edit it?
- Export (FBX, glTF, VRM, OBJ): you can view or upload it; the artist may not get clean layers, modifiers, or UVs to work with.
- Source (Blender .blend, project files, layered Substance): another artist can inspect and change systems — if your license allows sharing it.
- Baked textures, merged meshes, and export-only handoffs turn "small edits" into rebuilds. See source files and small edits.
3. Target fit — was this base built for where you need it?
- VRM file is portable 3D avatar data — it is not the same as a finished VRChat upload. Unity, SDK, PhysBones, and performance rank work may still be required.
- Poly count, rig type, bone naming, and expression setup must match your engine, tracker, or platform — not just "it looks fine in a screenshot."
- If the base style does not match what you want, "edit" may really mean redesign — price it that way.
When a base actually saves money
- VRoid self-serve when you want a standard anime avatar and accept VRoid's design limits.
- Marketplace base when the license explicitly covers your use and the mesh already fits the target.
- Team-owned base mesh with clean internal documentation and editable source.
- You only need a change the base pipeline supports — e.g. texture swap on separated materials, not a new body silhouette.
When a base costs you more than starting fresh
- Export-only handoff when the artist needs source to retopo, re-UV, or re-rig.
- Commercial or resale plans when the base license forbids them.
- VRChat as the goal when you only have a VRM and nobody scoped Unity upload work.
- Dense, baked, or stitched mesh where every edit re-opens the same problems — see Frankenstein models.
What to send before you ask for a quote
- The actual base files — not only screenshots or a rendered video.
- The license link or terms for the base and any parts inside it.
- Your target: OBS tracker, VRChat, Unity, game engine, resale, etc.
- Whether you need export only or editable source back.
- A written list of what you want changed — and what must still work after (tracking, outfits, expressions).
What to ask the artist
- What must you rebuild vs what can you tweak on this base?
- Does my license allow you to receive and modify these files for my use case?
- Will you test in my stack before calling it done?
- If the base forces a rebuild, is that a separate quote line?
- Who owns the derivative work, and does the base licensor allow it?
DJP interpretation: I have had "I have a base" mean a paid VRoid with one outfit change — and mean a Daz export that needed a week of retopo before anyone would rig it. Same client sentence, completely different job. Send the file and license first. Let the artist open it before you fight about whether the edit should cost $50 or $500.
License note: Base asset terms vary by marketplace and generator. Your commission contract should name what the base licensor allows — not assume "I bought it" covers commercial streaming or resale.