Support & Help Center

Send to Eagle communicates with Eagle on the same computer via http://127.0.0.1:41595 or http://localhost:41595. Ensure Eagle is installed and running and its local API is accessible. Eagle saves need this connection; copying or downloading share cards does not.

Eagle save history and preferences are stored locally in the browser. Page GraphQL requests and responses used to resolve original images and videos are handled in memory; authentication templates are not persisted. Functional requests go to X, media sources and local Eagle, not a project-operated content collection server. This does not mean no network requests occur. Old library data and authentication templates are no longer accessed and are not automatically cleared on update.

The extension uses an in-browser WebAssembly FFmpeg engine to remux Twitter HLS video fragments into standard MP4 files locally. Media availability and quality depend on the available source; not every video is available in 4K or original quality.

Yes. In the capture modal, you can search and select any existing Eagle folder, add tags, and your preferences are automatically remembered for subsequent saves.

X captures keep the original post link and author details. Post text and selected author replies can be edited before saving them as Eagle item notes. Click the extension icon to review today’s saves in the side panel. On other websites, right-click to save an image or page bookmark to Eagle.