𝗣𝗮𝗽𝗲𝗿 𝗦𝘂𝗺𝗺𝗮𝗿𝗶𝘀𝗲𝗿, 𝗬𝗼𝘂𝗿 𝗔𝗜-Powered 𝗔𝗿𝗫𝗶𝘃 𝗖𝗼𝗽𝗶𝗹𝗼𝘁

A powerful Chrome extension that automatically summarizes academic papers from arXiv using Google's Gemini AI. Get structured, easy-to-understand summaries of complex research papers with just one click.

Features

• 📄 PDF Text Extraction: Automatically extracts text from arXiv papers
• 🤖 AI-Powered Summaries: Uses Google's Gemini AI for high-quality, structured summaries
• 📝 Markdown Formatting: Clean, well-formatted summaries with proper headings and sections
• 🎯 Structured Output: Organized summaries covering:
  • Title and Authors Overview
  • Key Research Objectives
  • Methodology
  • Main Findings
  • Significant Contributions
  • Practical Applications
  • Limitations and Future Work
• 🖱️ User-Friendly Interface:
  • Draggable popups
  • Loading animations
  • Clean, modern design
  • Easy paper selection

Demo Video

demo.1.mp4

Installation

Prerequisites

• Node.js (v14 or higher)
• npm (comes with Node.js)
• Google Chrome (or any Chromium browser)

Pre-Compiled

• Go to releases, select the newest version.
• Follow instructions given.

Building from scratch

1. Clone the Repository

   git clone https://github.com/Talha-Ali-5365/Paper_Summarizer.git
   cd Paper_Summarizer

2. Install Dependencies

   npm install

3. Build the Extension

   npm run build

4. Load in Chrome

   • Open Chrome browser
   • Go to chrome://extensions/
   • Enable "Developer mode" (toggle in top-right)
   • Click "Load unpacked"
   • Select the dist folder from your project directory

API Key Setup

1. Get your API key for either: Gemini 2.0 Flash Thinking (Google AI Studio), DeepSeek R1 (OpenRouter), OpenAI o3-mini (GitHub models)
2. When on arXiv, click the gear (⚙) icon.
3. Select your choice of model and enter your API key.

Usage

1. Visit any paper on arXiv.org
2. The extension icon will appear in your Chrome toolbar
3. Click on a paper in the search results
4. Click "Summarize Selected Paper"
5. Wait for the summary to be generated
6. View the formatted summary in a draggable popup

Development

Project Structure

PaperSummarizer/
├── src/                    # Source code
│   ├── app.js             # Core functionality & API integration
│   ├── content.js         # UI/UX & content script
│   ├── popup.js           # Extension popup
│   └── background.js      # Background script
├── public/                # Static files
│   ├── manifest.json      # Extension configuration
│   ├── popup.html        # Popup interface
│   └── styles.css        # Global styles
├── package.json          # Dependencies & scripts
└── webpack.config.js     # Build configuration

Development Workflow

1. Start Development Server

   npm run dev

   This will watch for changes and rebuild automatically.

2. Making Changes

   • Edit files in the src directory
   • The extension will rebuild automatically
   • Refresh the extension in Chrome to see changes

3. Building for Production

   npm run build

Debugging

• Check the Chrome console for errors
• Extension logs will appear in the console
• API response data is logged for debugging
• Check network requests for API calls

Technical Details

Core Components

1. PDF Processing (app.js)

   • Uses PDF.js for text extraction
   • Handles large documents by chunking
   • Manages API communication

2. UI/UX (content.js)

   • Creates and manages popups
   • Handles user interactions
   • Implements loading states
   • Formats summaries using markdown

3. Extension Configuration (manifest.json)

   • Permissions
   • Content scripts
   • Resource access

Dependencies

• pdf.js: PDF text extraction
• axios: API requests
• marked: Markdown rendering
• webpack: Building and bundling

Troubleshooting

Common Issues

1. Extension Not Loading

   • Verify the dist folder exists
   • Check manifest.json for errors
   • Ensure Developer mode is enabled

2. PDF Not Processing

   • Check console for PDF.js errors
   • Verify file permissions
   • Ensure PDF URL is accessible

3. API Errors

   • Verify API key is correct
   • Check rate limits
   • Monitor network requests

Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For issues, questions, or contributions:

• Open an issue on GitHub
• Submit a pull request
• Contact the maintainers

---

Built with ❤️ for researchers and students