Typography
Aa
One clear system family
Use the native sans stack with confident weight contrast. Headlines are compact and balanced; body text stays generous and readable at 65 characters or less.
6440281816
Brand System · Version 2.0 · July 2026
PDFCheck design system.
A practical reference for making every PDFCheck journey feel familiar: clear hierarchy, obvious next actions, useful reassurance, and document evidence that is easy to understand.
PDFCheck
Original document icon, now reusable as SVG
The interface should help a first-time visitor choose a PDF, understand what happens next, and trust the result.
01
Foundations from the current homepage
Keep the current system font, green action hierarchy, light gray surfaces, compact radii, and generous centered sections. Improve consistency without making PDFCheck look like a different product.
Color
Verification green, anchored by ink
Slate text and white surfaces match the current homepage. Green communicates progress, primary action, and successful verification; pale green supports emphasis without overpowering the content.
50
#f0fdf4100
#dcfce7300
#86efac500
#22c55e600
#16a34a700
#15803d900
#14532d950
#052e16Form & rhythm
Corners
8–14px for product surfaces. Pills only for compact tags and status.
Spacing
Use an 8px base with intentionally wider 48–96px narrative gaps.
Borders
Use quiet full borders for structure. Never colored side stripes as decoration.
Motion
Fast, direct, and optional. Never hide content behind an entrance animation.
02
Current homepage, made more coherent
These examples retain the homepage’s centered hierarchy, green CTAs, bordered white surfaces, trust signals, and practical product language while improving flow and consistency.
Lead with the decision, then show the product working.
No signup needed · Files never stored
Free PDF Metadata Viewer & PDF Checker Online
View metadata, detect AI-generated content, check edit history, and verify authenticity. No signup required.
PDF files up to 100MB · instant resultsReplace generic metrics with concrete operating promises.
Built for decisions that need evidence.
Private by defaultAutomatic file deletion
Useful immediatelyClear results, no setup
Broad PDF coverageChecks, edits, conversion
Use editorial rhythm and a task list instead of another card grid.
One PDF workspace. Every practical task.
Organize tools by the outcome people need, with enough context to choose confidently.
Explore all PDF tools →A real ordered sequence is where numbered structure earns its place.
From file to clear answer.
Keep the process short enough to understand before upload, and specific enough to build trust.
- 1Choose your PDFUpload directly from your device.
- 2We inspect the signalsMetadata, structure, software, and safety checks run together.
- 3Act on a readable reportSee findings, next steps, and the right follow-up tool.
04
One outline icon language
Reuse the current homepage and tools-directory icons. They are simple 24px line drawings with rounded terminals, recognizable metaphors, and no decorative containers unless the surface needs grouping.
05
Core assets and working previews
Use the reusable logo component and existing social-card routes. Do not recreate or distort the mark per surface.
Primary lockup for light navigation, documentation, and product surfaces.
Inverse lockup for near-black brand surfaces and high-contrast placements.
06
UX principles to check before shipping
Use these principles as the final review checklist. They describe how PDFCheck should behave, not merely how it should look.
Make the next action obvious
One primary action per decision point. Secondary actions should help someone evaluate the product without competing with upload or completion.
Explain before asking
Before upload, say what the tool checks, what happens to the file, and what the result will contain. Do not rely on reassurance badges alone.
Show evidence in context
Keep the filename, status, evidence, and recommended action visually connected so users never need to infer which result belongs to which file.
Use progressive disclosure
Lead with the overall result and important exceptions. Keep raw metadata and technical detail available without forcing every user through it.
Never fabricate confidence
Use real counts, ratings, quotes, and compatibility claims only. When proof is unavailable, state a verifiable product fact instead.
Use proof people can verify
Social proof should reduce uncertainty near the upload decision. Prefer public availability, maintained integrations, and supported languages over vague popularity claims or invented counters.
Built for real document workflows
A compact proof block can sit below the first product interaction or before the wider tool suite.
A public, verifiable distribution channel users can inspect.
Documented integration for agent-assisted PDF workflows.
A concrete product capability supported by the current interface.
Do not publish a rating, customer count, testimonial, or “trusted worldwide” claim until the source and update process are documented.