LiquidText to Readwise: A Workaround for Preserving Highlight Relationships

LiquidText, a popular PDF reader for iPad, allows users to highlight text fragments and create visual relationships between them. However, when importing these highlights into Readwise—the service that helps users revisit highlights via regular emails—the grouped connections are lost. A new workaround by developer Greg Wolanski addresses this gap, enabling users to maintain the structural relationships between their highlights during the import process.

The workaround involves a manual but straightforward process that leverages LiquidText's sharing capabilities and a custom tool. Here's how it works:

1. Export from LiquidText: Open LiquidText on your iPad, select a book, and use the Share function to choose "LiquidText File." Then select "Another App" and send the file to your computer.

2. Process the File: Once on your computer, select the LiquidText file. The tool will prompt you to enter the book's title and author(s).

3. Download Improved Highlights: The processed file will now include the highlight relationships. Download this enhanced version.

4. Import to Readwise: Upload the improved highlights file directly into Readwise to import both the highlights and their groupings.

This method can be repeated for multiple LiquidText files, allowing users to systematically transfer their annotated library while preserving the contextual relationships they built in LiquidText.

The workaround highlights a common challenge in knowledge management tools: preserving interconnected data during migrations. While both LiquidText and Readwise serve the niche of digital annotation and review, their data formats aren't natively compatible for relationship preservation. This DIY solution demonstrates how users can bridge gaps in tool ecosystems through creative workflows.

For developers, this case underscores the importance of API design and data portability in productivity tools. As users increasingly rely on specialized software for knowledge work, seamless interoperability becomes a critical factor in long-term tool adoption. Future integrations between annotation platforms would benefit from standardized formats for preserving relationships—beyond simple text highlights—to support more complex knowledge graphs.

The workaround is currently available at Greg Wolanski's blog, where users can access the processing tool and detailed instructions. While manual, it offers a practical solution for users invested in both platforms who wish to maintain their research structures across tools.