1. Input Source (PNG, JSON, or YAML)
Format Quirks: Pygmalion vs. The World
The Pygmalion format has several unique naming conventions that our tool handles during the normalization process:
1. Prefix-Based Keys
Most formats use name or persona. Pygmalion adds a char_ prefix to almost everything (e.g., char_name, char_greeting). Our converter identifies your character's name and greeting from the source and applies these prefixes correctly.
2. Flat Schema Logic
Unlike modern V2 cards which can have nested "extensions," Pygmalion is a "flat" format. We strip out unnecessary metadata like "creator notes" or "frontend versioning" to keep the file as clean and compatible as possible for older systems.
3. World Scenario Mapping
In SillyTavern, the scenario is often its own field. In Pygmalion, this maps to world_scenario. We ensure the setting of your roleplay is preserved during the transition.
Who still uses Pygmalion JSON?
This tool is primarily designed for:
- Developers: Testing new models that expect the foundational Pygmalion dataset format.
- Archive Enthusiasts: Converting characters from old Discord repositories or early character hubs.
- JSON Editors: Users who want to manually tweak character data in a text editor like VS Code before final deployment.
FAQ: Classic Pygmalion Format
A: Yes. SillyTavern is backwards-compatible and can import the older Pygmalion JSON format, though it may ask you to "Migrate" the card to V2 after importing.
A: The Pygmalion JSON format is text-only. If you want a character with an image, use our "Any to TavernAI PNG" tool instead.
