Comparison
An importer that
does not hide complexity.
TildEka compared with Arvess public claims and native Tilda import. No marketing scores — only concrete fields and workflows.
All capabilitiesImport contract
What happens to the layout
This table follows the current documentation and the project’s technical audit from September 6, 2026.
| Capability | TildEka | Arvess | Native Tilda |
|---|---|---|---|
| Account and access recovery | |||
| Breakpoint count | Any | Any | Editor-limited |
| Text and mixed styles | Partial | ||
| Automatic image upload | Placeholder | Manual | |
| SVG as vector | Partial | ||
| Auto Layout / Flex | Partial | ||
| Naming and diagnostics | Matrix + recovery | Preflight | No |
| Slider / tabs / accordion | Runtime | Markers | Manual |
| Pixso | |||
| Media quality modes | 3 modes |
“—” means “not stated” or “not relevant to the workflow”, not a claim that a product can never do it.
Summary
TildEka’s edge is verifiability
After import you can reopen the model and see which fields, assets and interactions actually survived. That is more useful than a vague “pixel-perfect” promise.
No fixed limitassets in one package