Import & troubleshoot
Why some X likes are missing from your library
Separate a paused import, an upload problem, and unavailable source history with a step-by-step checklist.
Check the account and search scope first
A missing search result, an unfinished import, and a post X no longer provides are different problems. First confirm that you are signed into the Likes Library account connected to the extension, and that the extension detected the X account you intended to import.
In the dashboard, clear the search and choose All liked posts. A filter for one author can hide a post that is already stored. If you remember a specific post, try a short distinctive word from its text rather than reconstructing an entire sentence.
Make sure collection is still running
The browser import needs the X import tab to stay visible. Switching to a different tab pauses collection; returning lets it resume. If you closed your browser, reopen the import tab and continue. Check the extension’s status before starting repeated imports.
Collection from X and uploading to your library are separate steps. A temporary connection problem can leave posts waiting to upload. Restore the connection, keep the connected extension enabled, and check whether the queue progresses. Posts waiting for AI categories are already a different stage: categorization does not determine whether their text can be searched.
Check import access and recent likes
The free import is limited, and larger imports require a subscription. Check Settings for your account’s import access if collection stops at an allowance. Deleting stored posts does not restart that allowance, so clearing your library is not a useful troubleshooting step.
Likes made on another device are not automatically observed by your desktop extension. Run another import to collect posts that are now available in the X likes timeline. Existing post IDs are merged, so returning to the same timeline does not add duplicate copies.
Check which archive files you uploaded
For archive imports, make sure you uploaded the extracted like files and every relevant part. The whole ZIP is not a supported upload. Files containing your own tweets do not substitute for like files. A Likes Library JSON export is also supported.
Look for the missing post’s ID in the source file if you know it. If the archive lacks that record, the importer cannot create it. If the ID is present but text or author information is sparse, the library may preserve that limited record. See the archive guide for file selection.
A count difference does not identify the cause
The library stores unique imported posts. X’s displayed like count, the number of items the browser returns, archive records, and your unique saved posts are different measurements. Overlapping sources are merged rather than counted twice. Some source records lack details.
Deleted posts, inaccessible posts, and history that X stops returning may be unavailable before an import. A library count alone cannot show which explanation applies. If you already saved a post, failing to see it in a later import does not by itself remove that saved record.
Collect useful details before contacting support
Send support@likes-library.com the import method, the status or error message, whether the tab stayed visible, and a public post link if relevant. For an archive, include the file names and whether it has multiple parts.
Do not send passwords, extension connection tokens, or the full account archive. Those are unnecessary for an initial diagnosis. Keep a backup of the posts you have collected before making major changes to your account.