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
NUMBERS at a glance
NUMBERS
Numbers emerged as part of Apple's iWork suite, which offered a different design and document philosophy from Microsoft Office.
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 | NUMBERS | CUR |
|---|---|---|
| File type | Not available | Not available |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | Not available | Not available |
| File size characteristics | Not available | Not available |
| Compatibility | Not available | Not available |
| Editability | Not available | Not available |
| Created year | Not available | Not available |
| Inventor | Not available | Not available |
| Status | Not available | Not available |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | Not available | Not available |
| Metadata handling | Not available | Not available |
| Delivery profile | Not available | Not available |
| Workflow fit | Not available | Not available |
| Vector scaling | Not available | Not available |
When to use each format
When to use NUMBERS
- analysis
- reporting
- business-data exchange
- Important in Apple productivity workflows.
When to use CUR
- capture ingest
- editing
- web or print delivery
- Relevant for Windows resource compatibility.
FAQs
Why convert NUMBERS to CUR?
Choose CUR as target when preparing or preserving cursor assets for Windows applications, themes, or interface restoration.
What changes when converting NUMBERS 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 should I review after converting NUMBERS to CUR?
After conversion, review these destination checks: Open converted output in Windows resource tools and verify behavior on real samples; Compare output against the expected depends quality profile; Not mainstream web or publishing image targets.
How can I keep quality stable in NUMBERS to CUR conversion?
Run representative samples, keep settings deterministic, and monitor these risks: The workflow value is strongly platform-specific; Not mainstream web or publishing image targets; Validate destination compatibility before large-batch conversion.