Skip to content

Enhancement: Replace generic favicon with project-branded favicon #414

Description

@MeghPatel-007

✨ Feature Overview

Replace the current generic/default browser favicon with a project-branded favicon that better represents pdfToPng’s identity and improves visual consistency across the application.

Currently, the browser tab icon does not align with the application's branding and makes the project less recognizable when multiple tabs are open.


🚀 Why is this Feature Needed?

A branded favicon improves:

  • Better project identity and recognition
  • More polished and professional appearance
  • Easier tab identification when multiple browser tabs are open
  • Consistent visual experience across the website

This is a small UI enhancement with noticeable usability and branding benefits.


🎨 Visuals (If applicable)

Attach a screenshot of the current browser tab favicon.

Suggested direction:

  • Use project logo or simplified icon
  • Match existing color palette and branding
  • Maintain readability at small sizes

🔧 Possible Implementation (Optional)

Possible areas to update:

  • frontend/public/favicon.ico
  • frontend/public/favicon.png
  • frontend/index.html
  • Update <link rel="icon">
  • Verify favicon rendering after Vite build

Recommended:

  • Provide 32×32 and 16×16 versions
  • Optimize for dark/light browser themes

💡 Additional Notes

This change is purely visual and should not affect existing functionality.

Cross-browser validation (Chrome, Edge, Firefox) may be helpful.


🏆 Are you contributing under any open-source program?

Yes — GSSoC 2026

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions