Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
Drop files or choose a source
Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.
Max 2GB per file · Drag & drop ready · Mixed file types welcome
HWP at a glance
HWP
HWP's importance comes from regional software and government/business usage patterns rather than from global office-suite dominance.
CUR at a glance
CUR
These formats reflect how desktop operating systems built their own graphics-resource conventions for cursors, icons, and device-independent drawing.
Format comparison
| Feature | HWP | CUR |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1989 | 1990 |
| Inventor | Hancom | Microsoft / Windows ecosystem |
| Status | active | legacy |
| Primary use cases |
|
|
| Vector scaling | Not supported | Not supported |
When to use each format
When to use HWP
- Your source file is already in HWP.
- Preserve source expectations before exporting to CUR.
- HWP is commonly used in document workflows.
When to use CUR
- Your target workflow expects CUR.
- Improve delivery compatibility with CUR.
- CUR is commonly used in image workflows.
FAQs
Why convert HWP to CUR?
Convert to CUR when preparing or preserving cursor assets for Windows applications, themes, or interface restoration.
It is useful when pointer hotspot behavior must survive alongside the bitmap itself.
What changes when converting HWP to CUR?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting HWP to CUR?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.