1. Upload Pygmalion JSON

Technical Documentation: Bridging the Classics

The migration from **Pygmalion** to **KoboldAI** is a technical process of aligning two of the AI community's foundational data standards. While both schemas focus on local-first character storage, KoboldAI's format is primarily designed to save the state of a model's context for inference backends, whereas the Pygmalion standard serves as a generalized prefix-based bridge.

1. Semantic Field Alignment

Pygmalion characters utilize explicit key prefixes like char_name, char_persona, and world_scenario. KoboldAI (specifically in its lite frontends and backends) utilizes a more traditional JSON structure. Our converter identifies these classic prefixes and performs a "Semantic Alignment," ensuring that the character's internal logic remains cohesive during the transition, allowing the character to perform consistently across different inference environments.

2. Dialogue and Context Sanitization

Standard Pygmalion files are often optimized for 1-on-1 roleplay text completion. KoboldAI backends, such as KoboldCPP, are often more sensitive to the formatting of dialogue examples. Our conversion engine identifies and reformats dialogue within the example_dialogue field to ensure it adheres to the standardized patterns that maximize character "stickiness" without "token leaking" legacy artifacts that might trigger formatting errors in the Kobold interface.

3. World Info and Lore Extraction

Both Pygmalion and KoboldAI users rely heavily on lore persistence. While Pygmalion files often contain flattened scenario data, KoboldAI can handle more robust context management. Our tool ensures that the core narrative intent of your Pygmalion characters is meticulously preserved in the scenario and description blocks of the new Kobold JSON, providing the backend with the best possible starting point for generating relevant, character-aligned responses.

4. Privacy and Data Sovereignty

Because character development often involves hundreds of hours of creative writing, we prioritize security. Our tool utilizes a "Zero-Server" architecture, where all JSON processing is handled by your browser's local JavaScript. Your character files are never transmitted to our server, cached, or seen by any third party. This ensures that you maintain full ownership and control over your creative digital assets as you move them between the industry's foundational standards.

5. Identity Integrity and Backend Readiness

By outputting a standardized KoboldAI JSON, we ensure that your Pygmalion characters are ready for instant use in any backend that supports the Kobold save standard. This conversion process isn't just about moving data; it's about future-proofing your digital characters and ensuring they remain accessible, editable, and compatible with the broader AI ecosystem, regardless of which local inference tool you choose to use.